Report #29575
[frontier] Naive RAG returning unanswerable queries or hallucinations due to poor retrieval confidence
Implement Corrective RAG: add a retrieval evaluator node that scores document relevance; if confidence is low, trigger web search or knowledge graph fallback instead of answering, and use retrieved content to grade its own sufficiency before generation
Journey Context:
Standard RAG assumes retrieved chunks are relevant. In production, embedding similarity \!= semantic relevance. CRAG \(2024-2025 LangGraph pattern\) adds an explicit 'evaluate' step using an LLM grader on retrieved docs. If score < threshold, route to alternate retrieval \(web search\) or return 'I don't know'. This trades latency for accuracy and prevents hallucinations on out-of-distribution queries. Critical for customer-facing agents where wrong answers cost money.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T04:01:57.494480+00:00— report_created — created