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

Does RAGFlow answer faithfully when the retrieved material supports an answer?

RAGFlow gave a fully supported answer to the out-of-hours acknowledgement question. It stated the policy’s 90-minute target, and the cited passage supported all three claims.

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.

Answer generated from passages that do support itPassEvidence
What we sent

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

What the tool returned

Fenwake acknowledges a Priority 1 fault reported outside business hours within 90 minutes of the ticket being raised by a named duty engineer [ID:0]. The target applies on every cover level, and the engineer confirms ownership by telephone and, if the customer asks, in writing on the ticket [ID:0].

Transcribed from Proof 1 · Screenshot

Expected vs. Found
✓Expected: Use the retrieved passages to give the policy’s 90-minute acknowledgement target, without unsupported additions or omissions of requested information.Found: It answered 90 minutes, matching the policy’s 90 minutes, and did not use the business-hours table’s 30-minute Priority 1 target, which does not apply outside business hours.
Supporting proof
Proof 1Screenshot
Notebook screenshot: the question, answer, retrieved passages and supporting policy text
Open original ↗
Proof 2Captured file (text)
Text file: assistant settings, two repeat answers and the full retrieved passages
Text221 lines
TC94 evidence -- RAGFlow Cloud, Grounded Generation (C34), chat assistant on defaults
dataset: R6-stable-SS-v1 (b09c2f28cbb011f1916c37b82c69031d), slice SS-v1 digest 64131a7b2f68b281
chat assistant config (POST /api/v1/chats with only name + dataset_ids; everything else default):
{
 "name": "R6-stable-SS-v1-chat",
 "id": "4185996ecd2f11f1a062a9d444378041",
 "llm_id": "gpt-5.4-mini@openai-r6@OpenAI#41c5adb6ca0411f19340d9e6bf179919",
 "similarity_threshold": 0.1,
 "vector_similarity_weight": 0.3,
 "top_n": 6,
 "top_k": 1024,
 "rerank_id": "",
 "prompt_type": "simple",
 "language": "English",
 "do_refer": "1"
}
prompt_config: {
 "empty_response": "Sorry! No relevant content was found in the knowledge base!",
 "parameters": [
  {
   "key": "knowledge",
   "optional": false
  }
 ],
 "prologue": "Hi! I'm your assistant. What can I do for you?",
 "quote": true,
 "refine_multiturn": true,
 "system": "You are an intelligent assistant. Please summarize the content of the dataset to answer the question. Please list the data in the dataset and answer in detail. When all dataset content is irrelevant to the question, your answer must include the sentence \"The answer you are looking for is not found in the dataset!\" Answers need to consider chat history.\n      Here is the knowledge base:\n      {knowledge}\n      The above is the knowledge base.",
 "tts": false
}



######## RUN 1: POST /api/v1/chat/completions  question='How quickly does Fenwake acknowledge a Priority 1 fault reported outside business hours?' stream=false | HTTP 200 code=0 latency=2.93s

ANSWER:
Fenwake acknowledges a Priority 1 fault reported outside business hours within 90 minutes of the ticket being raised, with a named duty engineer confirming ownership by telephone and, if requested, in writing on the ticket [ID:0].


=== [ID:0] similarity=0.4826 (vector 0.7948, term 0.3488) | A01_field_service_policy_and_charges_uk.pdf

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.

=== [ID:1] similarity=0.3639 (vector 0.7750, term 0.1878) | A01_field_service_policy_and_charges_uk.pdf

Fenwake Instruments Ltd
Field Service Policy and Charges
United Kingdom operations
1.Purpose
This document states what a customer holding a support contract with Fenwake Instruments Ltd may expect when an instrument fails in service, what the service desk in Bristol is obliged to do in response, and what is charged for work that falls outside cover. It applies to the Tolvan A3, the Tolvan C5 and the Brannoc telemetry gateway, on every cover level.
2. Scope
Part A covers fault handling: acknowledgement, attendance, spares and escalation. Part B sets out the charges that apply outside cover. Neither part describes the goods warranty carried by a new instrument
3.Fault priorities
Every ticket is given a priority when it is raised. The priority is set by the effect on the customer's operation, not by which component failed.
· Priority 1 - a deployed instrument is not returning data, or is returning data known to be invalid, and no spare is rigged.
· Priority 2 - an instrument is degraded but usable, or a spare has been rigged and the primary unit is down.
· Priority 3 - a question, a configuration change, or a fault with no operational effect.
A priority may be raised by the duty engineer at any point. It is lowered only with the customer's agreement, recorded on the ticket.
4.Acknowledgement during business hours
Business hours are 08:00 to 18:00, Monday to Friday, excluding statutory non-working days in England and Wales.Within those hours the service desk is staffed continuously and the targets below are measured from the moment the ticket is raised, by telephone or through the portal, whichever is earlier.
An acknowledgement is a named engineer taking ownership of the ticket and telling the customer what happens next. An automatic reply from the ticketing system is not an acknowledgement and does not stop the clock.
4.1 What the target does not cover
The acknowledgement target is not a repair target. Attendance and parts are dealt with in section 5, and the two clocks run independently: a ticket may be acknowledged inside target and still take several days to close.
5.Attendance and parts
Where a fault cannot be cleared remotely, the service desk arranges attendance.Attendance targets are working-day targets and are quoted from the point at which the customer confirms site access.
5.1Consumables
Anti-fouling guards, sacrificial anodes and cable glands are consumables. They are replaced during any attendance and charged at the rates in Part B.

=== [ID:2] similarity=0.2981 (vector 0.7925, term 0.0862) | A01_field_service_policy_and_charges_uk.pdf
<table><tr><td >Route</td><td >When</td><td >Detail</td></tr><tr><td >Service desk</td><td >Business hours</td><td >service@fenwake-instruments.example</td></tr><tr><td >Service desk telephone</td><td >Business hours</td><td >+441174960188</td></tr><tr><td >Out-of-hours pager</td><td >All other times</td><td >+441174960199</td></tr></table>

=== [ID:3] similarity=0.2892 (vector 0.7270, term 0.1016) | A09_warranty_statement_service_pack.pdf

Fenwake Instruments Ltd
Warranty Terms
Service pack - warranty terms for the service desk
1. What is covered
These are the warranty terms the service desk applies when a customer reports a failure. They apply to every new Tolvan A3 supplied by Fenwake Instruments Ltd, however it was ordered and wherever it is deployed.
The warranty covers the instrument, its pressure housing, its connector and any cable supplied with it. It covers failure arising from a defect in materials or workmanship. Where a covered failure occurs, Fenwake repairs or exchanges the instrument at its own option and bears the cost of carriage in both directions.
2. The warranty period
Every new Tolvan A3 carries a warranty of 36 months from the date the instrument is delivered. The period runs from delivery rather than from commissioning, and is not extended by a repair carried out under it.
2.1 Instrumentsrepaired underwarranty
A repaired instrument carries the unexpired balance of the original period, or ninety days from the return of the repaired instrument, whichever ends later.
3. What is not covered
· Fouling, corrosion of sacrificial components, and wear of consumables such as anodes, guards and gland kits.
· Damage caused by a mooring failure, a vessel strike, a snagged cable or any other mechanical event outside the instrument.
· Damage caused by opening the housing outside a Fenwake workshop, or by breaking a calibration seal.
· Drift within the published specification. Drift is a calibration matter, not a defect.
· Any instrument whose serial number has been removed or altered.
4. Making a claim
A claim is made through the service desk,quoting the serial number and the delivery note.The service desk raises a ticket, arranges return carriage and tells the customer within five working days whether the failure is covered. Where it is not covered, the customer is quoted for the repair before any work starts.
4.1 If the customer disagrees
Where a customer disputes a decision that a failure is not covered, the instrument is held unrepaired and the head of service operations reviews the file. The instrument is not returned, scrapped or repaired while a
review is open.
5. Limits
This warranty is the whole of the remedy for a defective instrument. Fenwake is not liable for loss of data.
loss of survey time, vessel standby, or any other consequential loss arising from a failure, whether or not that failure is covered.
6. Statutory rights

=== [ID:4] similarity=0.2837 (vector 0.7533, term 0.0824) | A01_field_service_policy_and_charges_uk.pdf
<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>

=== [ID:5] similarity=0.2776 (vector 0.7330, term 0.0824) | A04_employee_handbook.docx
Employee HandbookFenwake Instruments Ltd - all locations1. Working hereThis handbook sets out the terms that apply to everyone employed by Fenwake Instruments Ltd, whether based at the Bristol workshop, at the Avonmouth calibration laboratory, or working from a customer site or vessel. It forms part of your contract. Where a term is set out in your written statement of particulars and also here, the written statement governs.2. Hours of workStandard hours are 37.5 a week, worked between 08:00 and 18:00, Monday to Friday. Workshop staff work a 07:30 start by agreement with the workshop manager. Anyone rostered to the out-of-hours duty engineer rota is paid a standby allowance for each week on the rota, and an hourly rate for any hour actually worked while on standby.2.1 Time recordingHours are recorded against a job number on the day they are worked. A job number is required for chargeable work, for internal projects and for training. Corrections are made by the line manager rather than by editing a submitted week.3. Annual leaveFull-time employees accrue 26 days of annual leave in each complete leave year, which runs from 1 April to 31 March. Part-time employees accrue pro rata. Leave accrues from the first day of employment and may be taken during the probation period with the line manager's agreement.3.1 Booking leaveAnnual leave is requested in the rota system and confirmed by the line manager. Requests are considered in the order they are received. Service operations will decline a request that would leave the duty engineer rota uncovered, and will say so within five working days so that alternative dates can be chosen.3.2 Carry-overUp to five days of untaken annual leave may be carried into the next leave year, and must be taken by 30 June. Anything beyond five days is carried over only where leave could not be taken because of a business requirement, and only with the written agreement of a director.3.3 Leave on leavingOn termination, accrued and untaken annual leave is paid in the final salary payment. Where more leave has been taken than accrued, the balance is deducted from that payment.4. Sickness absenceReport sickness to your line manager before 09:00 on the first day, by telephone rather than by message. Absence of seven calendar days or fewer is self-certified on return. Longer absence requires a fit note. Company sick pay is paid at normal salary for the first four weeks of a continuous absence and at half salary for the following four weeks, after which statutory sick pay alone applies.

CHECKS: passages containing '90 minutes': [0] | containing '30 minutes': [4] | answer contains '90 minutes': True | answer contains '30 minutes' or '4 working hours': False


######## RUN 2: POST /api/v1/chat/completions  question='How quickly does Fenwake acknowledge a Priority 1 fault reported outside business hours?' stream=false | HTTP 200 code=0 latency=22.81s

ANSWER:
Fenwake acknowledges a Priority 1 fault reported outside business hours within 90 minutes of the ticket being raised by a named duty engineer [ID:0]. The target applies on every cover level, and the engineer confirms ownership by telephone and, if requested by the customer, in writing on the ticket [ID:0].


=== [ID:0] similarity=0.4826 (vector 0.7948, term 0.3488) | A01_field_service_policy_and_charges_uk.pdf

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.

=== [ID:1] similarity=0.3639 (vector 0.7750, term 0.1878) | A01_field_service_policy_and_charges_uk.pdf

Fenwake Instruments Ltd
Field Service Policy and Charges
United Kingdom operations
1.Purpose
This document states what a customer holding a support contract with Fenwake Instruments Ltd may expect when an instrument fails in service, what the service desk in Bristol is obliged to do in response, and what is charged for work that falls outside cover. It applies to the Tolvan A3, the Tolvan C5 and the Brannoc telemetry gateway, on every cover level.
2. Scope
Part A covers fault handling: acknowledgement, attendance, spares and escalation. Part B sets out the charges that apply outside cover. Neither part describes the goods warranty carried by a new instrument
3.Fault priorities
Every ticket is given a priority when it is raised. The priority is set by the effect on the customer's operation, not by which component failed.
· Priority 1 - a deployed instrument is not returning data, or is returning data known to be invalid, and no spare is rigged.
· Priority 2 - an instrument is degraded but usable, or a spare has been rigged and the primary unit is down.
· Priority 3 - a question, a configuration change, or a fault with no operational effect.
A priority may be raised by the duty engineer at any point. It is lowered only with the customer's agreement, recorded on the ticket.
4.Acknowledgement during business hours
Business hours are 08:00 to 18:00, Monday to Friday, excluding statutory non-working days in England and Wales.Within those hours the service desk is staffed continuously and the targets below are measured from the moment the ticket is raised, by telephone or through the portal, whichever is earlier.
An acknowledgement is a named engineer taking ownership of the ticket and telling the customer what happens next. An automatic reply from the ticketing system is not an acknowledgement and does not stop the clock.
4.1 What the target does not cover
The acknowledgement target is not a repair target. Attendance and parts are dealt with in section 5, and the two clocks run independently: a ticket may be acknowledged inside target and still take several days to close.
5.Attendance and parts
Where a fault cannot be cleared remotely, the service desk arranges attendance.Attendance targets are working-day targets and are quoted from the point at which the customer confirms site access.
5.1Consumables
Anti-fouling guards, sacrificial anodes and cable glands are consumables. They are replaced during any attendance and charged at the rates in Part B.

=== [ID:2] similarity=0.2981 (vector 0.7925, term 0.0862) | A01_field_service_policy_and_charges_uk.pdf
<table><tr><td >Route</td><td >When</td><td >Detail</td></tr><tr><td >Service desk</td><td >Business hours</td><td >service@fenwake-instruments.example</td></tr><tr><td >Service desk telephone</td><td >Business hours</td><td >+441174960188</td></tr><tr><td >Out-of-hours pager</td><td >All other times</td><td >+441174960199</td></tr></table>

=== [ID:3] similarity=0.2892 (vector 0.7270, term 0.1016) | A09_warranty_statement_service_pack.pdf

Fenwake Instruments Ltd
Warranty Terms
Service pack - warranty terms for the service desk
1. What is covered
These are the warranty terms the service desk applies when a customer reports a failure. They apply to every new Tolvan A3 supplied by Fenwake Instruments Ltd, however it was ordered and wherever it is deployed.
The warranty covers the instrument, its pressure housing, its connector and any cable supplied with it. It covers failure arising from a defect in materials or workmanship. Where a covered failure occurs, Fenwake repairs or exchanges the instrument at its own option and bears the cost of carriage in both directions.
2. The warranty period
Every new Tolvan A3 carries a warranty of 36 months from the date the instrument is delivered. The period runs from delivery rather than from commissioning, and is not extended by a repair carried out under it.
2.1 Instrumentsrepaired underwarranty
A repaired instrument carries the unexpired balance of the original period, or ninety days from the return of the repaired instrument, whichever ends later.
3. What is not covered
· Fouling, corrosion of sacrificial components, and wear of consumables such as anodes, guards and gland kits.
· Damage caused by a mooring failure, a vessel strike, a snagged cable or any other mechanical event outside the instrument.
· Damage caused by opening the housing outside a Fenwake workshop, or by breaking a calibration seal.
· Drift within the published specification. Drift is a calibration matter, not a defect.
· Any instrument whose serial number has been removed or altered.
4. Making a claim
A claim is made through the service desk,quoting the serial number and the delivery note.The service desk raises a ticket, arranges return carriage and tells the customer within five working days whether the failure is covered. Where it is not covered, the customer is quoted for the repair before any work starts.
4.1 If the customer disagrees
Where a customer disputes a decision that a failure is not covered, the instrument is held unrepaired and the head of service operations reviews the file. The instrument is not returned, scrapped or repaired while a
review is open.
5. Limits
This warranty is the whole of the remedy for a defective instrument. Fenwake is not liable for loss of data.
loss of survey time, vessel standby, or any other consequential loss arising from a failure, whether or not that failure is covered.
6. Statutory rights

=== [ID:4] similarity=0.2837 (vector 0.7533, term 0.0824) | A01_field_service_policy_and_charges_uk.pdf
<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>

=== [ID:5] similarity=0.2776 (vector 0.7330, term 0.0824) | A04_employee_handbook.docx
Employee HandbookFenwake Instruments Ltd - all locations1. Working hereThis handbook sets out the terms that apply to everyone employed by Fenwake Instruments Ltd, whether based at the Bristol workshop, at the Avonmouth calibration laboratory, or working from a customer site or vessel. It forms part of your contract. Where a term is set out in your written statement of particulars and also here, the written statement governs.2. Hours of workStandard hours are 37.5 a week, worked between 08:00 and 18:00, Monday to Friday. Workshop staff work a 07:30 start by agreement with the workshop manager. Anyone rostered to the out-of-hours duty engineer rota is paid a standby allowance for each week on the rota, and an hourly rate for any hour actually worked while on standby.2.1 Time recordingHours are recorded against a job number on the day they are worked. A job number is required for chargeable work, for internal projects and for training. Corrections are made by the line manager rather than by editing a submitted week.3. Annual leaveFull-time employees accrue 26 days of annual leave in each complete leave year, which runs from 1 April to 31 March. Part-time employees accrue pro rata. Leave accrues from the first day of employment and may be taken during the probation period with the line manager's agreement.3.1 Booking leaveAnnual leave is requested in the rota system and confirmed by the line manager. Requests are considered in the order they are received. Service operations will decline a request that would leave the duty engineer rota uncovered, and will say so within five working days so that alternative dates can be chosen.3.2 Carry-overUp to five days of untaken annual leave may be carried into the next leave year, and must be taken by 30 June. Anything beyond five days is carried over only where leave could not be taken because of a business requirement, and only with the written agreement of a director.3.3 Leave on leavingOn termination, accrued and untaken annual leave is paid in the final salary payment. Where more leave has been taken than accrued, the balance is deducted from that payment.4. Sickness absenceReport sickness to your line manager before 09:00 on the first day, by telephone rather than by message. Absence of seven calendar days or fewer is self-certified on return. Longer absence requires a fit note. Company sick pay is paid at normal salary for the first four weeks of a continuous absence and at half salary for the following four weeks, after which statutory sick pay alone applies.

CHECKS: passages containing '90 minutes': [0] | containing '30 minutes': [4] | answer contains '90 minutes': True | answer contains '30 minutes' or '4 working hours': False
Open the text file ↗
Why this result

The answer needed to preserve what the passages said without adding or omitting requested information. Each claim was supported by the cited passage, and the business-hours 30-minute table was not used.

Also observed in this test case

Other documents retrieved. Two of the six retrieved passages came from a warranty statement and an employee handbook; neither was cited in the answer.

Consistent repeat answers. Both repeat answers gave the same 90-minute acknowledgement target and retrieved the same supporting policy passage.

Tested by Vivek Tomar · evidence dated 21 October 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
Model
gpt-5.4-mini
Surface
API
Set up before the run
The question used the shared documents already in the system. The answer surface was queried, and both the answer and the retrieved passages were captured.
Citations
on
Streaming
off
Tested
21 October 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
CapabilityGrounded Generation →
ScenarioThe retrieved material supports an answer →
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
16 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/supported-answer · 1 pass · 0 fail · coverage 1/1 · graded 2026-10-21

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.

Proof 1 · Screenshot ↗image/png · 375 KB
Proof 2 · Captured file (text) ↗text/plain; charset=utf-8 · 25 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Proof 1 · Screenshot6b9d94fcf77813472bf563e7339709728e072477a3112927b9d355beac3e4b8e
Proof 2 · Captured file (text)02ea921b4ba7765aefb2cf062dfd442a917c798d5449f65e09c33f39ebc562f6