generate tons of phrases and responses based mostly on common information, however what occurs once we want solutions requiring correct and particular information? Solely generative fashions regularly battle to offer solutions on area particular questions for a bunch of causes; possibly the info they had been educated on at the moment are outdated, possibly what we’re asking for is actually particular and specialised, possibly we would like responses that have in mind private or company knowledge that simply aren’t public… 🤷♀️ the listing goes on.
So, how can we leverage generative AI whereas holding our responses correct, related, and down-to-earth? reply to this query is the Retrieval-Augmented Technology (RAG) framework. RAG is a framework that consists of two key elements: retrieval and technology (duh!). In contrast to solely generative fashions which might be pre-trained on particular knowledge, RAG incorporates an additional step of retrieval that enables us to push further data into the mannequin from an exterior supply, similar to a database or a doc. To place it in a different way, a RAG pipeline permits for offering coherent and pure responses (offered by the technology step), that are additionally factually correct and grounded in a information base of our alternative (offered by the retrieval step).
On this means, RAG could be a particularly worthwhile software for functions the place extremely specialised knowledge is required, as as an example buyer help, authorized recommendation, or technical documentation. One typical instance of a RAG utility is buyer help chatbots, answering buyer points based mostly on an organization’s database of help paperwork and FAQs. One other instance could be complicated software program or technical merchandise with in depth troubleshooting guides. Another instance could be authorized recommendation — a RAG mannequin would entry and retrieve customized knowledge from regulation libraries, earlier instances, or agency tips. The examples are actually limitless; nonetheless, in all these instances, the entry to exterior, particular, and related to the context knowledge permits the mannequin to supply extra exact and correct responses.
So, on this publish, I stroll you thru constructing a easy RAG pipeline in Python, using ChatGPT API, LangChain, and FAISS.
What about RAG?
From a extra technical perspective, RAG is a method used to reinforce an LLM’s responses by injecting it with further, domain-specific data. In essence, RAG permits for a mannequin to additionally have in mind further exterior data — like a recipe ebook, a technical guide, or an organization’s inside information base — whereas forming its responses.
This is essential as a result of it permits us to get rid of a bunch of issues inherent to LLMs, as as an example:
- Hallucinations — making issues up
- Outdated data — if the mannequin wasn’t educated on current knowledge
- Transparency — not realizing the place responses are coming from
To make this work, the exterior paperwork are first processed into vector embeddings and saved in a vector database. Then, once we submit a immediate to the LLM, any related knowledge is retrieved from the vector database and handed to the LLM together with our immediate. In consequence, the response of the LLM is shaped by contemplating each our immediate and any related data current within the vector database within the background. Such a vector database could be hosted domestically or within the cloud, utilizing a service like Pinecone or Weaviate.

What about ChatGPT API, LangChain, and FAISS?
The primary part for constructing a RAG pipeline is the LLM mannequin that can generate the responses. This may be any LLM, like Gemini or Claude, however on this publish, I can be utilizing OpenAI’s ChatGPT fashions by way of their API platform. With a purpose to use their API, we have to sign up and acquire an API key. We additionally want to verify the respective Python libraries are put in.
pip set up openai
The opposite main part of constructing a RAG is processing exterior knowledge — producing embeddings from paperwork and storing them in a vector database. The preferred framework for performing such a activity is LangChain. Particularly, LangChain permits:
- Load and extract textual content from numerous doc sorts (PDFs, DOCX, TXT, and many others.)
- Break up the textual content into chunks appropriate for producing the embeddings
- Generate vector embeddings (on this publish, with the help of OpenAI’s API)
- Retailer and search embeddings by way of vector databases like FAISS, Chroma, and Pinecone
We are able to simply set up the required LangChain libraries by:
pip set up langchain langchain-community langchain-openai
On this publish, I’ll be utilizing LangChain along with FAISS, an area vector database developed by Fb AI Analysis. FAISS is a really light-weight package deal, and is thus applicable for constructing a easy/small RAG pipeline. It may be simply put in with:
pip set up faiss-cpu
Placing the whole lot collectively
So, in abstract, I’ll use:
- ChatGPT fashions by way of OpenAI’s API because the LLM
- LangChain, together with OpenAI’s API, to load the exterior recordsdata, course of them, and generate the vector embeddings
- FAISS to generate an area vector database
The file that I can be feeding into the RAG pipeline for this publish is a textual content file with some info about me. This textual content file is situated within the folder ‘RAG recordsdata’.

Now we’re all arrange, and we are able to begin by specifying our API key and initializing our mannequin:
from openai import OpenAI # Chat_GPT API key api_key = "your key"
# initialize LLM
llm = ChatOpenAI(openai_api_key=api_key, mannequin="gpt-4o-mini", temperature=0.3)
Then we are able to load the recordsdata we need to use for the RAG, generate the embeddings, and retailer them as a vector database as follows:
# loading paperwork for use for RAG
text_folder = "rag_files"
all_documents = []
for filename in os.listdir(text_folder):
if filename.decrease().endswith(".txt"):
file_path = os.path.be a part of(text_folder, filename)
loader = TextLoader(file_path)
all_documents.prolong(loader.load())
# generate embeddings
embeddings = OpenAIEmbeddings(openai_api_key=api_key)
# create vector database w FAISS
vector_store = FAISS.from_documents(paperwork, embeddings)
retriever = vector_store.as_retriever()
Lastly, we are able to wrap the whole lot in a easy executable Python file:
def foremost():
print("Welcome to the RAG Assistant. Kind 'exit' to give up.n")
whereas True:
user_input = enter("You: ").strip()
if user_input.decrease() == "exit":
print("Exiting…")
break
# get related paperwork
relevant_docs = retriever.get_relevant_documents(user_input)
retrieved_context = "nn".be a part of([doc.page_content for doc in relevant_docs])
# system immediate
system_prompt = (
"You're a useful assistant. "
"Use ONLY the next information base context to reply the person. "
"If the reply just isn't within the context, say you do not know.nn"
f"Context:n{retrieved_context}"
)
# messages for LLM
messages = [
{"role": "system", "content": system_prompt},
{"role": "user", "content": user_input}
]
# generate response
response = llm.invoke(messages)
assistant_message = response.content material.strip()
print(f"nAssistant: {assistant_message}n")
if __name__ == "__main__":
foremost()
Discover how the system immediate is outlined. Basically, a system immediate is an instruction given to the LLM that units the habits, tone, or constraints of the assistant earlier than the person interacts. For instance, we might set the system immediate to make the LLM present responses like speaking to a 4-year-old or a rocket scientist — right here we ask to offer responses solely based mostly on the exterior knowledge we offered, the ‘Maria info’
So, let’s see what we’ve cooked! 🍳
Firstly, I ask a query that’s irrelevant to the offered exterior datasource, to ensure that the mannequin solely makes use of the offered datasource when forming the responses and never common information.

… after which I requested some questions particularly from the file I offered…

✨✨✨✨
On my thoughts
Apparently, it is a very simplistic instance of a RAG setup — there’s way more to contemplate when implementing it in an actual enterprise setting, similar to safety issues round how knowledge is dealt with, or efficiency points when coping with a bigger, extra practical information corpus and elevated token utilization. Nonetheless, I imagine OpenAI’s API is actually spectacular and presents immense, untapped potential for constructing customized, context-specific AI functions.
Liked this publish? Let’s be pals! Be part of me on