Separating Retrieval Failures From Generation Failures in RAG Evaluation
Score retrieval and generation separately: the pair of metrics localizes whether a bad RAG answer is a retriever or an LLM problem.
Topic
Evals, hallucination detection, and monitoring so you know when the system is actually working.
Score retrieval and generation separately: the pair of metrics localizes whether a bad RAG answer is a retriever or an LLM problem.
Reference-based evals compare output to a known correct answer; reference-free evals score intrinsic properties like grounding without ground truth.
Version prompts in Git for small eng teams, move to a prompt tool when non-engineers contribute, and gate every change on an eval suite.
If you log one thing in your RAG pipeline, log the final assembled prompt. It's the fastest path from 'bad answer' to root cause.
Mine failing production traces, store input plus retrieved chunks plus expected behavior, and version 50-100 focused cases in-repo.