Question
Separate a retrieval failure from an answer-generation failure
An excellent writer cannot quote the paragraph it never received.
Before you use it
- Use when
- A document-grounded assistant gives a wrong answer and the team immediately starts rewriting the prompt.
Keep this limit in mind
- Faithfulness to a wrong source is still wrong. Automated evaluation scores need checking and should not replace source-version verification.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
A question to ask
Was the necessary information present in the approved source collection? · Did retrieval supply that information with the right version and scope? · Does the answer accurately use the supplied evidence and answer the question?
Why it matters
Inspect the question, retrieved passages and answer as separate artifacts. Determine whether the needed evidence was available, retrieved and used correctly. Also check whether the answer addresses the actual question. These are different failure locations and may need different repairs.
An example
The current procedure is in the library, but retrieval returns an obsolete version. A more forceful writing prompt is not the first repair.
Check your result
The defect is assigned to a supported failure location with the relevant artifacts attached.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingSeparate a retrieval failure from an answer-generation failure
Evidence and sources
Ragas separates faithfulness to retrieved context, answer relevance and context relevance instead of treating response quality as a single property.
Faithfulness to an incorrect source is not factual truth, and automated estimates can misclassify errors.
Ragas: Automated Evaluation of Retrieval Augmented Generation · Evaluation framework
Edition and review
Version 0.1.0
No review details are supplied for this edition.