Skip to content

Commit

Permalink
Improved wording on Query Augmentation
Browse files Browse the repository at this point in the history
  • Loading branch information
Santiago Olivar committed Apr 26, 2024
1 parent 1fd22f7 commit e05b039
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion _posts/2024-03-23-RAG-Design-Tradeoffs.md
Original file line number Diff line number Diff line change
Expand Up @@ -188,7 +188,7 @@ When discussing augmentation, it's important to differentiate between two types:
- **Prompt Augmentation:** This occurs after retrieval and involves modifying the prompt that will be sent to the LLM to generate the final output. The main objective is to improve the generation of the final output with a given knowledge/context.

### 4.1. Query Augmentation
Query augmentation addresses the issue of how a query is phrased and whether it is optimal for finding relevant data to support the answer. Techniques for query transformation significantly enhance RAG performance, especially when dealing with short and vague user queries.
Query augmentation addresses the issue of how a query is phrased and whether it is optimal for finding relevant data to support the answer. Techniques for query transformation significantly enhance RAG performance and higher quality retrieved results, especially when dealing with short and vague user queries.

Here is a list of different query transformations:
- **Routing:** Retain the query but determine the relevant subset of pipelines that the query applies to.
Expand Down

0 comments on commit e05b039

Please sign in to comment.