Skip to main content
Deployment & Operations

Re-Ranker

A re-ranker is a second-stage retrieval model that re-scores a candidate set (typically top 50–100) from a fast first-stage retriever using a more expensive cross-encoder that jointly attends to query and document.

AIDOLS Research Team · Editorial standards

Full definition

Bi-encoders (used in vector search) embed query and document separately — fast but loses interaction. Cross-encoders concatenate query and document and run them through a transformer together — expensive but markedly more accurate: Nogueira and Cho's BERT re-ranker beat the previous MS MARCO state of the art by 27% (relative) in MRR@10. The standard pipeline retrieves top-100 with a bi-encoder, then re-ranks to top-5 with a cross-encoder. Production options: Cohere Rerank, Voyage Rerank, BGE-Reranker, Jina Reranker, Mixedbread.

Why it matters

Adding a re-ranker is the single highest-ROI quality improvement most enterprise RAG systems can make: Databricks reports an average 15-point gain in retrieval accuracy (recall@10) on its enterprise benchmarks, at roughly $0.001–0.01 per query in incremental cost. It should be the first optimization after a baseline RAG ships.

Example

A bank's policy-search system retrieves top-50 documents in 60ms with pgvector, then re-ranks with Cohere Rerank in 200ms; final-answer accuracy on a 200-question eval rises from 67% to 84%.

Next steps

More deployment & operations terms

Source & further reading

Primary source: Nogueira, Cho — "Passage Re-ranking with BERT" (2019).

Citation policy: this entry is part of the AIDOLS AI Implementation Glossary and may be quoted for research, journalism, and education with attribution to aidolsgroup.com/en/glossary/re-ranker/.