Report #5010
[architecture] Why does my RAG retrieve the wrong chunk even when the answer exists?
Prepend chunk-specific explanatory context to each chunk before embedding it and before building the BM25 index.
Journey Context:
Standard chunking strips referential context: a chunk reading 'revenue grew 3%' is useless without knowing the company and quarter. Generic document summaries add little. Anthropic's contextual retrieval generates 50-100 tokens of situating context per chunk using the LLM, then embeds and indexes the contextualized chunk. This reduced top-20 retrieval failure by 49% and, combined with reranking, by 67%. The win comes from preprocessing, not from a more expensive embedding model.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T20:30:33.508863+00:00— report_created — created