Can RAGFlow trace a claim back to its source?
RAGFlow’s out-of-hours Priority 1 answer cited text supporting all four claims, including acknowledgement within 90 minutes of the ticket being raised. The retrieved table giving 30 minutes was not cited.
1 of 1 test case passed
Every test case in this scenario has a result.
The test case
Each test case is judged on its own: Pass, Fail, Not gradable, or Untested. The scenario result above is based on this test case.
Citation opened and read against the claim it supportsPassEvidence
“How quickly does Fenwake acknowledge a Priority 1 fault reported outside business hours?”
Fenwake acknowledges a Priority 1 fault reported outside business hours within 90 minutes of the ticket being raised, by a named duty engineer who confirms ownership by telephone and, if requested, in writing on the ticket [ID:0].
API response: the answer, its citation and the supporting and uncited passages
Copied from Output file (text), line 22
Open the text file ↗| ✓ | Expected: The citation must lead to text supporting the answer’s actual claims, not just the same document or topic.Found: Both answer and cited passage specify acknowledgement within 90 minutes of ticket creation, a named duty engineer, ownership confirmed by phone and, on request, in writing on the ticket. |
The citation needed to substantiate the answer, not just identify a relevant document. It supported the response time, responsible engineer and both forms of ownership confirmation. The default prompt was unchanged.
Four-page citation target. The answer’s citation points to pages 3 to 6 as a single block, rather than a specific page or line. The supporting sentence must be found within that block.
Configuration and setup
How this tool was set up for the run and what the test needed in place. Each row is a fact from the run's records; a fact the records do not hold is left out, not guessed.
How this scenario is graded
How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.
Each test case gets one result per tool: Pass, Fail or Not gradable. A test case we haven't run yet shows Untested. There are no partial results.
- Pass: the tool did everything the test expected, and nothing it said contradicts the correct answer.
- Fail: at least one expected behaviour clearly didn't happen; the test case's result says which one and quotes the tool.
- Not gradable: our evidence couldn't settle the outcome (for example a record we needed is missing). It is never counted as a fail, and the test case's result says what's missing.
Where this sits in the benchmark
This page is one cell of a larger study: one tool, one scenario. Only this benchmark's frame appears here.
| Level | Name | Scope |
|---|---|---|
| Benchmark | Managed RAG → | 15 scenarios · 9 tools |
| Capability | Citations → | |
| Scenario | A claim in the answer traced back to its source → | |
| Tool | RAGFlow → |
Global scenario definition → · Global capability definition →
History of this result
What has happened to this result since it was first published. Runs and grades are never overwritten: a retest or a re-grade publishes a new result and keeps the earlier one readable.
Act on this result
Nothing filed here edits the run or the grade. A challenge opens a review, and a review can produce a new run or a re-grade — which becomes the current result and leaves this one in the history.
You run the same kind of test against your own setup and get the same behaviour.
Agree →Yours behaves differently. Tell us what you got, with a screenshot if you have one.
Disagree →Something here is wrong — a reference value, a transcription, a grade.
Report an issue →Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.
Vendor notice →The same record is available as structured data through the AI Demos MCP server, with the counts, the coverage and every per-test-case reason carried as fields.
Verify the proof files
These files support this result. Open a file to inspect the original evidence.
File fingerprints (SHA-256)
A fingerprint identifies the exact file used for this result.