Hybrid Retrieval (2024) › The Solution
History of Language AIAll chapters Hybrid Retrieval (2024) › The SolutionOne section · Sections in this chapter3 / 7 ↓
Reading tools Definitions & inline links
Choose your expertise level to adjust how many terms are explained. Beginners see more tooltips, experts see fewer to maintain reading flow. Hover over underlined terms for instant definitions.
Article links
Make inline references clickable
Hybrid retrieval systems addressed these limitations by systematically combining sparse and dense retrieval methods so that each compensated for the other's weaknesses. The core architectural pattern was a two-stage retrieval pipeline that used sparse methods for fast candidate generation followed by dense methods for semantic reranking. This design enabled systems to process large document collections efficiently using sparse retrieval, then apply sophisticated semantic understanding using dense methods on a much smaller set of candidate documents, balancing efficiency and effectiveness in ways that neither approach could achieve alone.
The first stage of hybrid retrieval systems used sparse retrieval methods like BM25 for fast candidate generation. Given a query, sparse retrieval systems could rapidly identify potentially relevant documents from large collections using inverted index lookups that took milliseconds. This candidate generation stage typically retrieved hundreds or thousands of documents from collections containing millions or billions of documents, filtering the collection down to a manageable set of potentially relevant candidates. The sparse retrieval stage prioritized speed and recall, aiming to include all potentially relevant documents in the candidate set even if many non-relevant documents were also included. The computational efficiency of sparse retrieval made this broad candidate generation feasible even for very large document collections.
Hybrid retrieval systems use sparse methods for fast, broad candidate generation, then apply dense methods for precise semantic reranking. This architecture balances efficiency from sparse retrieval with effectiveness from dense methods, creating systems that outperform either approach alone.
The second stage of hybrid retrieval systems used dense neural retrieval methods for semantic reranking of the candidate documents. The dense reranking stage applied neural networks to encode queries and candidate documents into dense vector representations, then computed semantic similarity scores between query and document vectors. These semantic scores could capture meaning relationships that sparse retrieval missed, such as matching "automobile accidents" with "car crashes" or understanding that a query asking about "climate change impacts" should rank documents discussing "global warming effects" highly. The reranking stage operated on the much smaller candidate set from the first stage, making the computational cost of dense retrieval manageable even for real-time applications.
The scoring mechanism in hybrid retrieval systems typically combined scores from both stages. The final relevance score for a document might combine the sparse retrieval score from the first stage with the dense retrieval score from the reranking stage, using weighted combinations or learned fusion functions. This score fusion incorporated both lexical matching signals from sparse retrieval and semantic similarity signals from dense retrieval, producing ranking functions that worked across more query types than either approach alone. The combination of scores also provided a way to balance the strengths of each approach, giving more weight to sparse scores for exact matching queries and more weight to dense scores for semantic queries.
The training procedures for hybrid retrieval systems were adapted to work with both sparse and dense components. The dense reranking models were typically trained on query-document pairs with relevance labels, learning embeddings that captured semantic relationships between queries and relevant documents. The training process optimized the dense embeddings to rank relevant documents higher than non-relevant documents in the candidate set, learning patterns that complemented the sparse retrieval signals. Some systems also learned fusion functions that optimized how sparse and dense scores should be combined for different query types or domains, adapting the hybrid approach to specific applications.
The indexing procedures for hybrid retrieval systems maintained both sparse and dense representations. Documents were indexed using traditional inverted indexes for sparse retrieval, enabling fast keyword matching and candidate generation. Documents were also encoded into dense embeddings that could be used for reranking, with these embeddings pre-computed during indexing and stored for efficient access during retrieval. The dual indexing architecture enabled systems to use sparse retrieval for fast candidate generation while still having dense representations available for semantic reranking, supporting the two-stage retrieval pipeline efficiently.
Advanced hybrid retrieval systems explored more sophisticated architectures beyond simple two-stage pipelines. Some systems used learned retrieval where neural networks learned to combine sparse and dense signals directly, creating unified retrieval models that integrated both approaches. Other systems used cascade retrieval where multiple stages applied increasingly sophisticated ranking functions to progressively smaller candidate sets, using sparse retrieval for very broad filtering, intermediate retrieval for medium filtering, and dense retrieval for final ranking. These architectures varied how and where they combined sparse and dense methods, adapting the hybrid approach to different applications and requirements.
The effectiveness of hybrid retrieval systems was demonstrated by their superior performance on diverse retrieval tasks compared to pure sparse or pure dense methods. Hybrid systems achieved better retrieval quality on question answering datasets where semantic understanding mattered, while also maintaining strong performance on exact matching tasks where sparse methods excelled. Combining lexical precision with semantic understanding allowed the same system to handle different query types and user intents.