Can RAGFlow retrieve an answer available in its knowledge base?
RAGFlow retrieved the passage answering the knowledge-base question. The first result contained the 90-minute out-of-hours acknowledgement target; the business-hours passage ranked fifth.
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.
Naturally phrased question the corpus answersPassEvidence
“How quickly does Fenwake acknowledge a Priority 1 fault reported outside business hours?”
=== rank 1 | similarity=0.4826 | A01_field_service_policy_and_charges_uk.pdf | pages [3, 4, 5, 6]
5.2Access Where a site requires a permit, an induction or a vessel movement, the attendance clock is suspended until access is confirmed in writing. The suspension is recorded on the ticket with the reason. 6.Out-of-hours cover Outside business hours the service desk is not staffed. A duty engineer rota covers every hour of the year, and the out-of-hours number in section 8 pages the engineer on call. 6.1Acknowledgementout ofhours A Priority 1 fault reported outside business hours is acknowledged by a named duty engineer within 90 minutes of the ticket being raised. The engineer confirms ownership by telephone and, where the customer asks for it, in writing on the ticket. The target applies on every cover level; the cover level determines what happens after acknowledgement, not how quickly the call is answered. 6.2Whatfollows acknowledgement Having acknowledged, the duty engineer attempts a remote diagnosis using the telemetry record. Where the fault cannot be cleared remotely, attendance is arranged under section 5 from the start of the following working day, except on Critical cover, where the duty engineer may authorise attendance immediately 6.3Priority 2 and Priority 3 out of hours Priority 2 and Priority 3 tickets raised outside business hours are queued and acknowledged when the service desk opens. The business-hours targets in section 4 then apply from opening. 7.Escalation A customer may escalate at any time, and the service desk escalates on its own initiative when a target is missed. Each step below is a named person, not a queue. · Step 1 - Duty engineer. Owns the ticket and the diagnosis · Step 2 - Service desk lead. Owns the schedule, the parts and the customer communication. · Step 3 - Head of service operations. Owns the commercial consequences and any goodwill offered. · Step 4 - Operations director. Owns the relationship. A step is skipped only where the person is unavailable, and the skip is recorded. Escalation does not restart the acknowledgement clock, which is measured once per ticket. 7.1 Missed targets Where an acknowledgement target is missed, the service desk lead writes to the customer within one working day setting out what happened and what has changed. A missed target is reported in the monthly service review whether or not the customer raises it. 8. Contacts 9. Exclusions Part A does not apply where the instrument has been modified outside a Fenwake workshop, where a fault is caused by a third-party mooring or cable, or where a customer has declined a recommended firmware update in writing. In those cases the service desk will still respond, and work is quoted at the rates in Part B.
=== rank 5 | similarity=0.2836 | A01_field_service_policy_and_charges_uk.pdf | pages [2]
| Priority | Acknowledgement target | Measured from |
| Priority 1 | 30 minutes | Ticket raised |
| Priority 2 | 4 working hours | Ticket raised |
| Priority 3 | The next working day | Ticket raised |
Show the reply as returned (Markdown)
=== rank 1 | similarity=0.4826 | A01_field_service_policy_and_charges_uk.pdf | pages [3, 4, 5, 6] 5.2Access Where a site requires a permit, an induction or a vessel movement, the attendance clock is suspended until access is confirmed in writing. The suspension is recorded on the ticket with the reason. 6.Out-of-hours cover Outside business hours the service desk is not staffed. A duty engineer rota covers every hour of the year, and the out-of-hours number in section 8 pages the engineer on call. 6.1Acknowledgementout ofhours A Priority 1 fault reported outside business hours is acknowledged by a named duty engineer within 90 minutes of the ticket being raised. The engineer confirms ownership by telephone and, where the customer asks for it, in writing on the ticket. The target applies on every cover level; the cover level determines what happens after acknowledgement, not how quickly the call is answered. 6.2Whatfollows acknowledgement Having acknowledged, the duty engineer attempts a remote diagnosis using the telemetry record. Where the fault cannot be cleared remotely, attendance is arranged under section 5 from the start of the following working day, except on Critical cover, where the duty engineer may authorise attendance immediately 6.3Priority 2 and Priority 3 out of hours Priority 2 and Priority 3 tickets raised outside business hours are queued and acknowledged when the service desk opens. The business-hours targets in section 4 then apply from opening. 7.Escalation A customer may escalate at any time, and the service desk escalates on its own initiative when a target is missed. Each step below is a named person, not a queue. · Step 1 - Duty engineer. Owns the ticket and the diagnosis · Step 2 - Service desk lead. Owns the schedule, the parts and the customer communication. · Step 3 - Head of service operations. Owns the commercial consequences and any goodwill offered. · Step 4 - Operations director. Owns the relationship. A step is skipped only where the person is unavailable, and the skip is recorded. Escalation does not restart the acknowledgement clock, which is measured once per ticket. 7.1 Missed targets Where an acknowledgement target is missed, the service desk lead writes to the customer within one working day setting out what happened and what has changed. A missed target is reported in the monthly service review whether or not the customer raises it. 8. Contacts 9. Exclusions Part A does not apply where the instrument has been modified outside a Fenwake workshop, where a fault is caused by a third-party mooring or cable, or where a customer has declined a recommended firmware update in writing. In those cases the service desk will still respond, and work is quoted at the rates in Part B. === rank 5 | similarity=0.2836 | A01_field_service_policy_and_charges_uk.pdf | pages [2] <table><tr><td >Priority</td><td >Acknowledgement target</td><td >Measured from</td></tr><tr><td >Priority 1</td><td >30 minutes</td><td >Ticket raised</td></tr><tr><td >Priority 2</td><td >4 working hours</td><td >Ticket raised</td></tr><tr><td >Priority 3</td><td >The next working day</td><td >Ticket raised</td></tr></table>
Retrieval log: the question and all 15 ranked passages in full
Copied from Output file (text), lines 5–28
Open the text file ↗Copied from Output file (text), lines 85–87
| ✓ | Expected: Include the supporting passage among the retrieved results.Found: The first result says a named duty engineer acknowledges an out-of-hours Priority 1 fault within 90 minutes after the ticket is raised. |
The supporting passage was required among the results, and it appeared first. This retrieval call returns ranked passages, not a written answer.
Page range. The first-ranked chunk spans pages 3–6; page 4 is one of four pages listed for it.
Unrelated results. The 15 returned chunks include six from the document containing the answer. The rest come from unrelated documents, with similarity scores of 0.20–0.29.
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 | Retrieval → | |
| Scenario | Answer is available in the knowledge base → | |
| 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.