AI Demos Research — the structured-intelligence platform. Every verdict on these pages opens to the execution behind it.
Graded 17 November 2026

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.

Pass rate100%1 of 1 gradable
Coverage1 of 1test case with a result
1PassDid everything it was expected to do.
0FailNo test case failed.
0Not gradableEvery result here could be graded.
0UntestedEvery test case in this scenario has a result.
The pass rate is a summary. The evidence is the test case below: what we sent, what we checked, what the tool returned, and the proof.

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
What we sent

“How quickly does Fenwake acknowledge a Priority 1 fault reported outside business hours?”

What the tool returned
Text
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 vs. Found
✓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.
Supporting proof
Proof 1Screenshot
Notebook screenshot: the question, answer and opened citation text
Open original ↗
Why this result

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.

Also observed in this test case

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.

Tested by Vivek Tomar · evidence dated 7 November 2026

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.

Software that produced the output
RAGFlow
Build or version
v0.26.4
Plan or tier
Starter
Surface
API
Set up before the run
A multi-page Fenwake service policy was required for the out-of-hours Priority 1 question, with the relevant terms on page 4 and a decoy table on page 2. Each citation had to be opened and read.
Streaming
Off
Assistant configuration
Default prompt; only a name and datasets supplied
Tested
7 November 2026 · Vivek Tomar

How this scenario is graded

How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.

How results are decided

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.

The rules
  • 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.

LevelNameScope
BenchmarkManaged RAG →15 scenarios · 9 tools
CapabilityCitations →
ScenarioA claim in the answer traced back to its source →
ToolRAGFlow →

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.

from the publication record
18 November 2026First publishedManaged RAG v1

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.

This matches what I see

You run the same kind of test against your own setup and get the same behaviour.

Agree →
This does not match

Yours behaves differently. Tell us what you got, with a screenshot if you have one.

Disagree →
Point out an issue

Something here is wrong — a reference value, a transcription, a grade.

Report an issue →
Request a retest

On a newer build, a larger dataset, or your own setup.

Request a retest →
We have fixed this

Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.

Vendor notice →
Filed against this evidenceNothing yet. Challenges, counter-evidence and fix notices appear here with their outcome, and stay on the page after they are resolved.
Cite this result
aidemos.com/benchmarks/managed-rag/results/ragflow/a-claim-in-the-answer-traced-back-to-its-source · 1 pass · 0 fail · coverage 1/1 · graded 2026-11-17

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.

Output file (text) ↗text/plain; charset=utf-8 · 34 KB
Proof 1 · Screenshot ↗image/png · 232 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Output file (text)46d003b2b732968fdeb12b7e57c36e03376eb3995f778a0ac54ce93125ab37f8
Proof 1 · Screenshot12b822b07814b50638f97d18b074dd0676b0898666cbc59b610bfc1a79e59a46