Skip to main content

AI and prompt engineering

[PLACEHOLDER]

On this occasion we would like to present our take and summary about prompt engineering.

Like everyone else, at Beolle we have been researching the AI space lately, running experiments. On this occasion, our investigation has made us present our take and summary about prompt engineering.

(Skip Ahead note: If you like to get right to it then skip to the section What are prompts.)

Generated image with Microsoft Designer and DALL-E 3 + Modified by Beolle team

 

(Parenthesis)

 AI has disrupted all industries, and it will continue to do so as we explore new territories. We are still in discovery mode. Sectors and industries are building their know-how, evolving and using this technology;  determining the value it brings to the business.

The investment by tech players and executives, in traditional and Gen AI (Generative AI) capabilities, continues rising. The consequence has been an accelerated growth in a short matter of time. Venture capital investment in AI has grown 13x over the last ten (10) years.

Mckinsey partial image from report on GenAI impact on business


If you like to read more about the Mckinsey report, and get the full images then go to The economic potential of generative AI: The next productivity frontier. 

(Parenthesis - end) 


What are prompts?

Prompts are queries that users can provide to the Large Language Model (LLM) in order to bring forth responses. They enable us to interact with the model in plain, natural language. 

Prompt Engineering is asking the right question to get the best output from the LLM. 

Good Prompt Engineers will allow companies to get the best out of the AI models. They are creative and persistent, with good technical knowledge, an understanding of the models and the domain, as well as they are great at experimentation (exploring different parameters and settings for fine-tuning the prompts). Even though it would be a plus, you don’t need to know how to code.

By looking at the NLP progression, you can see how things have evolved to where we are (Well, at least at the time of this article creation as things continue evolving constantly and quickly in this space), which is prompt engineering:

Models/patterns Engineering progression
Initially we had supervised learning (Non-Neural Networks).
This could use SVM (Support Vector Machine), which is a type of supervised learning algorithm that can be leveraged, as an example, for classification and regression tasks.
Here is where Feature Engineering comes. This is when transforming the raw data into Features that can be used by ML models.
A Feature is a variable/attribute that serves as input.
Following, Supervised learning (Neural Networks).
Neural Networks are based on a collection of Artificial Neurons, called units. The units are organised within layers. The units are connected, passing signals (inputs) between them.
Architecture Engineering.
A way to look at this Engineering is the Long Short-Term Memory (LSTM). In LSTM the information (data) is gated by the layers, determining what data will be passing through the workflow, and which will be discarded.
Within this engineering you can leverage embeddings + LSTM for processing tasks such as classification and sentiment analysis.
Pre-train and fine-tuning.
Using pre-trained LMs.
Objective Engineering.
The model gets trained for an objective, meaning to perform a specific task.
The fine-tuning technique becomes handy, as you gain efficiency by taking an existing model and specialising it by feeding it the new datasets based on the needs of your specialisation.
Pre-train, prompt, predict.

Defining inputs that fits the model.

Prompt Engineering.

How to Structure your prompt 

  • Instruction. A statement that tells the model what is required. You can also frame the instruction as a question. 
  • Context. Information that can guide the model in a desired direction. 
  • Constraints. (Optional). This can be used to limit the scope by being explicit, keeping the focus on the context. 
  • Input data. (Optional). 
  • Examples. (Optional) The model will have further guidance regarding the answer, and its format, when examples are part of the prompt. Example: Provide a list with the 7 wonders of the world. Only use reliable sources, and list those sources.

Prompt Types

  • Direct prompting or Zero shot. It only contains the instruction in the prompt. 
    • Prompt: Can you give me a list of ideas for blog posts for tourists visiting New York City for the first time? 
  • Prompting with examples. 
    • One-shot. Instruction + one clear example. 
      • Prompt: Come up with a list of ideas for blog posts for visitors to South America. 
        • 1. Have you visited Machu Picchu? Here are a few tips
    • Few-shots. Instruction + more than one example. 
  • Chain-of-thought prompting: This type of prompt provides a series of related prompts to the model. 

Last thoughts

  1. Provide as many details as needed within your prompt. 
  2. Include the majority of the elements explained within the “How to structure your prompt” section. 
  3. Be mindful of hallucinations. Hallucinations are responses with contradictions or inconsistencies, plain and simple the responses are incorrect, either completely, or partially. Chain-of-thought-prompting can help reduce this risk as you request the LLM to explain its reasoning. 
  4. Play with the temperature parameter when prompting and working with LLMs. A higher temperature can move the model response farther from context as it yields to be more creative and open. While a lower one makes things more factual and accurate.

Trending posts

Steer for a talent transformation strategy (and avoiding AI fatigue)

 There was a debate on whether to feature the term “AI” in the title of this article. Honestly, a key motivation for pursuing the research that led to this post was sparked by the widespread excitement about AI appearing constantly in our LinkedIn feed, to the point of feeling the fatigue, and even a bit disappointed in the algorithm of this, and the others, social media and content curated apps.  We soon discovered that there is an entire concept called "AI fatigue", not exactly how we were feeling it, but more about the mixed emotions people in the workforce have regarding the use of AI tools. Photo by Mart Production via Pexels (background updated with AI and Adobe  tech) From micro blog posts to video podcasts, lately, most of the tech content we encounter revolves around AI. They often sound or read very similar, usually mentioning the same few top providers. The articles (and social posts... at least the popular ones with paid-campaigns behind it) tend to focus less...

Digital Sovereignty in a Polarised World - Data, Cloud Power, and the Search for Trusted Alternatives

 Relationships have deteriorated, with trust diminished to an extent that may preclude restoration. The world, once structured to favour certain regions, has undergone significant shifts; for numerous countries, such advantages never existed. In this polarised reality, stakeholders are re-evaluating alliances, as former partners now often embody the role of "frenemy," thereby threatening freedom. This phenomenon is longstanding, rooted in historical power dynamics. When politics and influence supersede principles of fairness, respect, and integrity, ethical boundaries become blurred. Previously, issues that did not directly affect you would get overlooked out of principle, but current risks necessitate action to safeguard sovereignty. Information has consistently served as a key strategic asset, a trend only intensified by technological advancements that have elevated data as the principal factor. In other words, technology has amplified that, and data is the name of the game...

Assembling MLOps practice - part 2

 Part I of this series, published in May, discussed the definition of MLOps and outlined the requirements for implementing this practice within an organisation. It also addressed some of the roles necessary within the team to support MLOps. Lego Alike data assembly - Generated with Gemini   This time, we move forward by exploring part of the technical stack that could be an option for implementing MLOps.  Before proceeding, below is a CTA to the first part of the article for reference. Assembling an MLOps Practice - Part 1 ML components are key parts of the ecosystem, supporting the solutions provided to clients. As a result, DevOps and MLOps have become part of the "secret sauce" for success... Take me there Components of your MLOps stack. The MLOps stack optimises the machine learning life-cycle by fostering collaboration across teams, delivering continuous integration and depl...

Building MCP with TypeScript

MCP servers are popular these days. We’ve been researching and exploring a few code repos, some where missing modularity, others just not having pieces that we were looking for… therefore we decided to build our own, simple and foundational that could be a starting point for those trying to solve for the similar things we were… and we decided to share it with the community, via our public github. MCP host, server,data sources     Before we start.  Using Typescript and NodeJS was one of our requirements. This proved somewhat challenging because I don't code as frequently these days due to my leadership responsibilities, and I typically prefer working with C# or Python. Colleagues in my tech community have been working with their teams on some of their MCPs going the Python route. Therefore, I said, “I guess we are trying the other route” 😊. One of our reasons to go with TypeScript was due to the need of the integration with APIs, and based on the research, it seems t...

This blog uses cookies to improve your browsing experience. Simple analytics might be in place for pageviews purposes. They are harmless and never personally identify you.

Agreed