While Large Language Models (LLMs) can answer questions on many topics, they may not correctly answer about the topics that are not included in the training data such as recent events, or deep web (i.e. data that is not indexed by search engines). Another missing piece is not getting exact source of the answer, making verification challenging. This is where Retrieval Augmented Generation (RAG) can be useful. RAG combines the generative capabilities of LLMs with information retrieval from external sources of data and also can cite the exact sources of its answers, greatly improving verifiability and reliability. In this article we will enhance RAG with Retrieval Augmented Fine-tuning.
Learning Objectives
Learners will identify the limitations of Large Language Models (LLMs) and understand how Retrieval Augmented Generation (RAG) enhances answer accuracy and reliability by incorporating external data.
Participants will learn how to prepare data for LLM fine-tuning, including chunking, question generation, and the selection of oracle and distractor contexts.
Learners will become familiar with configuring the RAFTDatasetPack parameters for optimal question and answer generation from LLMs.
Learn to comprehend how the Semantic Splitter Node Parser processes data into chunks and the significance of cosine dissimilarity in improving model understanding.
In RAG, we split the data into chunks, find the top-K most similar chunks to the query, and present those chunks of content to the LLM to generate an answer. However, those top-K chunks can contain a mix of relevant and irrelevant content for the given query. The LLM should be able to find the relevant content for the query among those chunks given to it to generate the answer. So, if we can finetune the LLM for this specific task of generating an answer given both relevant and irrelevant content in the prompt, it can improve the accuracy of RAG.
What is Retrieval Augmented Fine-tuning?
As shown in the above picture, generating an answer for a query based on only the training data is like a “closed book” exam. An “Open book” exam is where the answer is generated using external data, which RAG.
In a new method, we train the LLM about how to effectively use the external data. This method significantly improved the RAG performance (https://arxiv.org/pdf/2403.10131.pdf)
How to Prepare the Data for Fine-tuning the LLM?
Let us now dive deeper on how to prepare the data for Fine-tuning the LLM:
Dividing Sample Data: Segments the sample data into chunks. Each chunk represents a potential source of information or context for generating questions.
Generating Questions: Creates corresponding questions for every chunk of data. These questions are designed to be answerable using the information within the chunk.
Generate answer with Oracle Context: The ‘oracle context’ refers to the chunk of data that contains the precise information needed to answer a given question. Uses this context alongside the question to generate the answer using Chain of Thought prompting.
Selecting Distractor Contexts: In addition to the oracle context, a few random chunks of data are chosen as ‘distractor contexts’.These simulate noise and irrelevant information, challenging the model to focus on the relevant context.
Compiling Training Data: Compilers include the question, oracle context, distractor contexts, and the generated answer, alongside explicit instructions on how the model should discern and utilize the relevant context to answer questions, into a comprehensive training dataset.
Fine-Tuning the Model: Utilizing this dataset, the model undergoes fine-tuning, learning to accurately distinguish relevant from irrelevant information and to generate precise answers based on the context provided.
Implementation of Retrieval Augmented Fine-tuning
Let us now learn the implementation of Retrieval Augmented Fine-tuning. Initially we start with installing the required libraries using the following commands:
pip install llama-index
pip install llama-index-packs-raft-dataset
Then you can import the RAFTDataset:
from llama_index.packs.raft_dataset import RAFTDatasetPack
For the data preparation process for Q/A generation, the RAFTDatasetPack is configured with the following parameters:
filepath: Specifies the path of the file used to generate questions and answers. This file acts as the primary source of content for the dataset
llm: Defines the Large Language Model (LLM) employed for generating questions and answers. GPT-4 is used by default if no model is specified. Choose the model carefully by considering the costs.
embed-model: The embedding model used to calculate the similarity between a query and its context, essential for selecting relevant context chunks.
num_questions_per_chunk: It determines the number of questions to be created for each data chunk, directly affecting the comprehensiveness of the training dataset.
num_distract_docs: Sets the number of random context chunks used as distractors for each question, challenging the model to identify relevant information
chunk_size: Llama-index uses SemanticSplitterNodeParser to split the dataset into chunks. So, this parameter is not useful.
default_breakpoint_percentile_threshold: Controls the threshold for combining chunks based on their dissimilarity. A higher value results in fewer, larger chunks, affecting the granularity of the data used for training.
Semantic Splitter Node Parser
The SemanticNodeParser operates by dissecting the data at the sentence level, initially dividing the text into smaller segments or ‘chunks’. Here’s how the process unfolds:
Initial Chunk Formation: The system splits each sentence of the data into initial chunks.
Cosine Dissimilarity Calculation: For each pair of adjacent chunks, the parser calculates the cosine dissimilarity, which is (1- cosine similarity). This metric quantifies how different the chunks are from each other, based on their vector representations in a multi-dimensional semantic space.
Threshold for Concatenation: The system sets a pre-defined threshold for dissimilarity. When the dissimilarity between adjacent chunks exceeds this threshold, it indicates that the chunks are significantly different from each other.
Chunk Concatenation: When the dissimilarity does not exceed the threshold, indicating similarity or relevance between chunks, the system concatenates those chunks to form a larger, unified chunk. This process aims to ensure that each chunk represents a cohesive piece of information, enhancing the model’s ability to understand and process the data effectively.
Step1: Import Necessary Libraries
from llama_index.llms.openai import OpenAI
from llama_index.embeddings.huggingface import HuggingFaceEmbedding
Step2: Load OpenAI API Key Using Environment Variable File
import os
OPENAI_API_KEY = os.environ['OPENAI_API_KEY']
# create the dataset
dataset = raft_dataset.run()
# save the dataset in jsonl format
output_path = './raft_dataset'
dataset.to_json(output_path + ".jsonl")
Step5: Loading Dataset
with open('./raft_dataset.jsonl', 'r') as json_file:
dataset = list(json_file)
# We can access the dataset with the following
json.loads(dataset[0]).keys()
# output
# dict_keys(['id', 'type', 'question', 'context', 'oracle_context', 'cot_answer', 'instruction'])
json.loads(dataset[0])['question']
# output
# 'What were the two main things the author worked on before college?'
Key Takeaways
Learned that RAG significantly improves the performance of LLMs by integrating external data sources, enabling the models to generate more accurate, verifiable, and reliable answers, particularly for queries on topics not covered in their initial training data.
Fine-tuning LLMs with a carefully prepared dataset, including oracle and distractor contexts, enhances the model’s ability to discern relevant from irrelevant information, leading to more precise responses to complex queries.
Examined that Semantic Splitter Node Parser plays a crucial role in data preprocessing for LLM fine-tuning, by dividing data into semantically coherent chunks based on cosine dissimilarity, thereby optimizing the model’s training and subsequent performance.
Conclusion
The adoption of RAG alongside Large Language Models significantly mitigates their limitations by enabling accurate, verifiable responses to queries beyond their initial training scope. Fine-tuning LLMs with specifically prepared datasets and leveraging preprocessing techniques like the Semantic Splitter Node Parser enhances model performance. This approach marks a significant step forward in the evolution of AI applications, highlighting the importance of innovation in artificial intelligence for more reliable and sophisticated solutions.
Frequently Asked Questions
Q1. What is Retrieval Augmented Generation?
A. RAG is a technique that enhances Large Language Models (LLMs) by incorporating external data sources into their answering process. This allows LLMs to provide more accurate, verifiable, and up-to-date answers. Especially for queries about topics not included in their original training data.
Q2. How does fine-tuning improve LLM performance in this example?
A. LLMs’ ability to prioritize relevant information significantly improves when fine-tuned with a specific dataset, including both relevant and irrelevant contexts. This process leads to the generation of more precise and contextually accurate responses to complex queries.
Q3. What is the RAFT Dataset, and how does it relate to RAG?
A.The RAFT Dataset specifically designs for fine-tuning LLMs in a RAG setup. It includes a meticulously prepared dataset with questions, oracle contexts for correct answers, and distractor contexts to challenge the model. The setup teaches the LLM to efficiently utilize external data for precise and dependable responses, utilizing the RAG model’s strengths.
I am working as an Associate Data Scientist at Analytics Vidhya, a platform dedicated to building the Data Science ecosystem. My interests lie in the fields of Natural Language Processing (NLP), Deep Learning, and AI Agents.
We use cookies essential for this site to function well. Please click to help us improve its usefulness with additional cookies. Learn about our use of cookies in our Privacy Policy & Cookies Policy.
Show details
Powered By
Cookies
This site uses cookies to ensure that you get the best experience possible. To learn more about how we use cookies, please refer to our Privacy Policy & Cookies Policy.
brahmaid
It is needed for personalizing the website.
csrftoken
This cookie is used to prevent Cross-site request forgery (often abbreviated as CSRF) attacks of the website
Identityid
Preserves the login/logout state of users across the whole site.
sessionid
Preserves users' states across page requests.
g_state
Google One-Tap login adds this g_state cookie to set the user status on how they interact with the One-Tap modal.
MUID
Used by Microsoft Clarity, to store and track visits across websites.
_clck
Used by Microsoft Clarity, Persists the Clarity User ID and preferences, unique to that site, on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.
_clsk
Used by Microsoft Clarity, Connects multiple page views by a user into a single Clarity session recording.
SRM_I
Collects user data is specifically adapted to the user or device. The user can also be followed outside of the loaded website, creating a picture of the visitor's behavior.
SM
Use to measure the use of the website for internal analytics
CLID
The cookie is set by embedded Microsoft Clarity scripts. The purpose of this cookie is for heatmap and session recording.
SRM_B
Collected user data is specifically adapted to the user or device. The user can also be followed outside of the loaded website, creating a picture of the visitor's behavior.
_gid
This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected includes the number of visitors, the source where they have come from, and the pages visited in an anonymous form.
_ga_#
Used by Google Analytics, to store and count pageviews.
_gat_#
Used by Google Analytics to collect data on the number of times a user has visited the website as well as dates for the first and most recent visit.
collect
Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels.
AEC
cookies ensure that requests within a browsing session are made by the user, and not by other sites.
G_ENABLED_IDPS
use the cookie when customers want to make a referral from their gmail contacts; it helps auth the gmail account.
test_cookie
This cookie is set by DoubleClick (which is owned by Google) to determine if the website visitor's browser supports cookies.
_we_us
this is used to send push notification using webengage.
WebKlipperAuth
used by webenage to track auth of webenagage.
ln_or
Linkedin sets this cookie to registers statistical data on users' behavior on the website for internal analytics.
JSESSIONID
Use to maintain an anonymous user session by the server.
li_rm
Used as part of the LinkedIn Remember Me feature and is set when a user clicks Remember Me on the device to make it easier for him or her to sign in to that device.
AnalyticsSyncHistory
Used to store information about the time a sync with the lms_analytics cookie took place for users in the Designated Countries.
lms_analytics
Used to store information about the time a sync with the AnalyticsSyncHistory cookie took place for users in the Designated Countries.
liap
Cookie used for Sign-in with Linkedin and/or to allow for the Linkedin follow feature.
visit
allow for the Linkedin follow feature.
li_at
often used to identify you, including your name, interests, and previous activity.
s_plt
Tracks the time that the previous page took to load
lang
Used to remember a user's language setting to ensure LinkedIn.com displays in the language selected by the user in their settings
s_tp
Tracks percent of page viewed
AMCV_14215E3D5995C57C0A495C55%40AdobeOrg
Indicates the start of a session for Adobe Experience Cloud
s_pltp
Provides page name value (URL) for use by Adobe Analytics
s_tslv
Used to retain and fetch time since last visit in Adobe Analytics
li_theme
Remembers a user's display preference/theme setting
li_theme_set
Remembers which users have updated their display / theme preferences
We do not use cookies of this type.
_gcl_au
Used by Google Adsense, to store and track conversions.
SID
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
SAPISID
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
__Secure-#
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
APISID
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
SSID
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
HSID
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
DV
These cookies are used for the purpose of targeted advertising.
NID
These cookies are used for the purpose of targeted advertising.
1P_JAR
These cookies are used to gather website statistics, and track conversion rates.
OTZ
Aggregate analysis of website visitors
_fbp
This cookie is set by Facebook to deliver advertisements when they are on Facebook or a digital platform powered by Facebook advertising after visiting this website.
fr
Contains a unique browser and user ID, used for targeted advertising.
bscookie
Used by LinkedIn to track the use of embedded services.
lidc
Used by LinkedIn for tracking the use of embedded services.
bcookie
Used by LinkedIn to track the use of embedded services.
aam_uuid
Use these cookies to assign a unique ID when users visit a website.
UserMatchHistory
These cookies are set by LinkedIn for advertising purposes, including: tracking visitors so that more relevant ads can be presented, allowing users to use the 'Apply with LinkedIn' or the 'Sign-in with LinkedIn' functions, collecting information about how visitors use the site, etc.
li_sugr
Used to make a probabilistic match of a user's identity outside the Designated Countries
MR
Used to collect information for analytics purposes.
ANONCHK
Used to store session ID for a users session to ensure that clicks from adverts on the Bing search engine are verified for reporting purposes and for personalisation
We do not use cookies of this type.
Cookie declaration last updated on 24/03/2023 by Analytics Vidhya.
Cookies are small text files that can be used by websites to make a user's experience more efficient. The law states that we can store cookies on your device if they are strictly necessary for the operation of this site. For all other types of cookies, we need your permission. This site uses different types of cookies. Some cookies are placed by third-party services that appear on our pages. Learn more about who we are, how you can contact us, and how we process personal data in our Privacy Policy.