Skip to content

Commit

Permalink
Update index.md
Browse files Browse the repository at this point in the history
  • Loading branch information
TuanaCelik authored Aug 13, 2024
1 parent e1a573e commit 4a83780
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions content/blog/query-expansion/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,8 +5,8 @@ description: Expand keyword queries to improve recall and provide more context t
featured_image: thumbnail.png
images: ["blog/query-expansion/thumbnail.png"]
toc: True
date: 2024-08-12
last_updated: 2024-08-12
date: 2024-08-14
last_updated: 2024-08-14
authors:
- Tuana Celik
tags: ["Retrieval", "RAG", "Advanced Use Cases"]
Expand Down Expand Up @@ -223,4 +223,4 @@ Query Expansion is a great technique that will allow you to get a wider range of

This does however mean that we heavily rely on the quality of the provided query. Query expansion allows you to navigate this issue by generating similar queries to the user query.

In my opinion, one of the main advantages of this technique is that it allows you to avoid embedding documentation at each update, while still managing to increase the relevance of retrieved documents at query time. Keyword retrieval doesn’t require any extra embedding step, so the only inferencing happening at retrieval time in this scenario is when we ask an LLM to generate a certain number of similar queries.
In my opinion, one of the main advantages of this technique is that it allows you to avoid embedding documentation at each update, while still managing to increase the relevance of retrieved documents at query time. Keyword retrieval doesn’t require any extra embedding step, so the only inferencing happening at retrieval time in this scenario is when we ask an LLM to generate a certain number of similar queries.

0 comments on commit 4a83780

Please sign in to comment.