Pipelines RAG en plusieurs étapes
Concevez et mettez en œuvre des flux de travail RAG complexes comprenant plusieurs étapes de recherche et de génération pour produire des réponses nuancées.
Pipelines RAG en plusieurs étapes est une leçon Vector Databases: Pinecone, Weaviate & pgvector gratuite sur CoddyKit. Ceci est la leçon 2 sur 4. Tu peux lire la leçon complète ci-dessous gratuitement — puis la pratiquer en direct dans le navigateur avec un éditeur de code intégré et un tuteur IA 24/7. Elle fait partie du parcours d'apprentissage Vector Databases: Pinecone, Weaviate & pgvector, et ta progression se synchronise sur le web et l'application CoddyKit. Le cours Vector Databases: Pinecone, Weaviate & pgvector comprend 4 leçons au total.
Certaines parties de cette leçon n'ont pas encore été traduites et s'affichent en anglais.
What is Multi-Stage RAG?
Traditional RAG (Retrieval Augmented Generation) works well for straightforward questions. However, for complex or ambiguous queries, a single retrieval and generation step can often fall short.
Multi-stage RAG pipelines address this by breaking down the problem into several sequential steps, refining the search and generation process at each stage to produce more accurate and nuanced answers.
Why Go Multi-Stage?
A basic RAG setup might struggle with:
- Multi-part questions: "Who founded Apple and when was their first product released?"
- Ambiguous queries: Needing iterative clarification.
- Deep contextual understanding: Requiring information from disparate sources or multiple 'hops' in knowledge.
Multi-stage RAG enhances the system's ability to handle these challenges by processing information more thoroughly.
The Core Idea: Iterative Refinement
The essence of a multi-stage RAG pipeline is iterative refinement. Instead of one pass, the system performs multiple passes, where:
- Early stages generate intermediate results or refined queries.
- Later stages use these intermediate outputs to perform more targeted retrieval or generation.
Each step builds upon the previous one, leading to a more precise and comprehensive final answer.
Step 1: Query Decomposition
For intricate user questions, the first step often involves query decomposition. This means breaking down a complex query into a set of simpler, more focused sub-questions.
- Example: "Tell me about the founder of Python and when was it first released?"
- Decomposed: "Who founded Python?", "When was Python first released?"
Each sub-question can then be processed individually for more effective retrieval.
Step 2: Initial Context Retrieval
Once you have decomposed the original query into sub-questions, the next step is to perform an initial retrieval for each of these sub-queries.
This involves querying your vector database (or other knowledge sources) with each sub-question to gather a broad set of potentially relevant documents or text chunks. The goal is to collect all initial pieces of the puzzle.
Step 3: Intermediate Generation & Refinement
With the initial context retrieved, an LLM (Large Language Model) can be used to process this information. This intermediate step can involve:
- Generating intermediate answers: Providing partial answers to sub-questions.
- Formulating follow-up questions: Using initial context to generate new, more specific queries for a second retrieval pass.
- Summarizing initial findings: Condensing retrieved information to guide subsequent steps.
This feedback loop helps in refining the search.
Step 4: Re-ranking & Aggregation
After potentially multiple retrieval passes and intermediate generations, you'll have various pieces of context and potentially partial answers. The final stages involve:
- Re-ranking: Using a more powerful model or a different relevance score to select the most pertinent chunks from all retrieved documents.
- Aggregation: Combining all relevant information and intermediate answers to synthesize a single, comprehensive, and coherent final response to the original user query.
Multi-Hop Q&A Example
Consider a 'multi-hop' question: "What is the capital of the country where the Eiffel Tower is located?"
A multi-stage pipeline could:
- Hop 1: Retrieve information about the "Eiffel Tower" to identify its location (Paris, France).
- Hop 2: Use "France" as a new query to retrieve information about its capital (Paris).
- Final Answer: Combine to answer "Paris".
This chaining of retrieval steps is a powerful application of multi-stage RAG.
Python Workflow Illustration
This conceptual Python code illustrates the high-level orchestration of a multi-stage RAG pipeline. It focuses on the flow rather than specific external API calls.
class MultiStageRAG:
def __init__(self, retriever, llm_model):
self.retriever = retriever
self.llm = llm_model
def run_pipeline(self, user_query):
# Stage 1: Decompose query into sub-questions
sub_queries = self.llm.decompose_query(user_query)
print(f"Decomposed queries: {sub_queries}")
all_retrieved_docs = []
intermediate_answers = []
for sq in sub_queries:
# Stage 2: Initial Retrieval for each sub-query
docs = self.retriever.retrieve(sq)
all_retrieved_docs.extend(docs)
print(f"Retrieved for '{sq}': {len(docs)} docs")
# Stage 3: Intermediate Generation (e.g., summarizing, refining)
intermediate_ans = self.llm.generate_answer(sq, docs)
intermediate_answers.append(intermediate_ans)
# Stage 4: Re-rank all retrieved context and aggregate
final_context = self.retriever.re_rank(all_retrieved_docs)
print(f"Final context length: {len(final_context)}")
final_answer = self.llm.generate_final_answer(user_query, final_context)
return final_answer
# --- Mock Implementations for Demonstration ---
class MockRetriever:
def retrieve(self, query):
# Simulate retrieving documents based on query
return [f"Doc for '{query}' part A", f"Doc for '{query}' part B"]
def re_rank(self, docs):
# Simulate re-ranking, just returns the first few for simplicity
return docs[:3]
class MockLLM:
def decompose_query(self, query):
# Simple decomposition for example
if " and " in query:
parts = query.split(" and ")
return [p.strip() + "?" for p in parts]
return [query + "?"]
def generate_answer(self, query, docs):
# Simulate generating an intermediate answer
return f"Intermediate answer for '{query}' based on {len(docs)} docs."
def generate_final_answer(self, original_query, context):
# Simulate generating a final answer
return f"Final answer to '{original_query}' based on context: {context}."
# --- Main Execution ---
if __name__ == "__main__":
mock_retriever = MockRetriever()
mock_llm = MockLLM()
pipeline = MultiStageRAG(mock_retriever, mock_llm)
query = "What is the capital of France and who painted the Mona Lisa?"
result = pipeline.run_pipeline(query)
print(f"\nResult: {result}")
Multi-Stage Benefits
Which of the following is a primary benefit of using a multi-stage RAG pipeline compared to a single-pass RAG?
Recap: Mastering Complex RAG
We've explored multi-stage RAG pipelines, understanding how they tackle complex queries through iterative steps:
- Query Decomposition: Breaking down complex questions into simpler sub-queries.
- Iterative Retrieval: Performing multiple passes to gather and refine context.
- LLM Refinement: Using LLMs to generate intermediate answers or guide subsequent search steps.
- Aggregation: Combining all insights for a comprehensive and coherent final answer.
By orchestrating these steps, you can build RAG systems capable of delivering much more precise and thorough responses to even the most challenging user prompts.
Questions Fréquemment Posées
La leçon « Pipelines RAG en plusieurs étapes » est-elle gratuite ?
Oui — le texte complet de « Pipelines RAG en plusieurs étapes » est gratuit à lire ici sur le web. Pour la pratiquer de manière interactive (un éditeur de code intégré et un tuteur IA 24/7) et déverrouiller le reste du cours Vector Databases: Pinecone, Weaviate & pgvector, passe à CoddyKit PRO. Le cours Vector Databases: Pinecone, Weaviate & pgvector comprend 4 leçons au total.
Qu'est-ce que j'apprendrai dans « Pipelines RAG en plusieurs étapes » ?
Concevez et mettez en œuvre des flux de travail RAG complexes comprenant plusieurs étapes de recherche et de génération pour produire des réponses nuancées. Tu pratiques Vector Databases: Pinecone, Weaviate & pgvector avec du code pratique que tu exécutes directement dans le navigateur, et un tuteur IA 24/7 répond à tes questions au fur et à mesure que tu avances dans la leçon.
Dois-je avoir de l'expérience pour commencer Vector Databases: Pinecone, Weaviate & pgvector ?
Aucune expérience préalable n'est requise. Vector Databases: Pinecone, Weaviate & pgvector sur CoddyKit est structuré pour les débutants jusqu'aux apprenants avancés, donc tu peux commencer ici ou depuis le début et avancer à ton rythme. Ceci est la leçon 2 sur 4.
Combien de temps prend la leçon « Pipelines RAG en plusieurs étapes » ?
La plupart des leçons CoddyKit prennent environ 5–10 minutes. Chacune est courte et interactive, tu progresses régulièrement et tu repiques exactement où tu t'es arrêté sur le web et l'app.
Peux-tu écrire et exécuter du code dans cette leçon Vector Databases: Pinecone, Weaviate & pgvector ?
Oui. Chaque leçon Vector Databases: Pinecone, Weaviate & pgvector inclut un éditeur de code intégré, tu écris et exécutes du vrai code directement dans ton navigateur et tu reçois des retours IA instantanés — aucune configuration locale requise.
Toutes les leçons de ce cours
- Techniques de transformation des requêtes
- Pipelines RAG en plusieurs étapes
- Évaluer les performances d’un système RAG
- Rer classer les résultats récupérés