Report #103252
[frontier] Why does my RAG pipeline retrieve the wrong chunks even when the answer is in the document?
Use contextual retrieval: prepend a short document-level context sentence to each chunk before embedding, combine dense and sparse retrieval with reranking, and set chunk boundaries by semantic or logical units instead of fixed token sizes.
Journey Context:
Fixed-size chunking loses document context, producing false matches. Anthropic's contextual retrieval cut failures by 49-67%. In 2025-2026 production RAG is becoming a hybrid of contextual embeddings, keyword search, graph traversal, and rerankers, with query-class routing. The shift is from 'one RAG pipeline' to a mixture of retrieval strategies chosen per question.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-10T05:16:24.360022+00:00— report_created — created