Can FutureSmart Document Intelligence answer from retrieved material that contains the answer?
FutureSmart Document Intelligence produced an answer that is supported by the passages in view. The checked passage supports the out-of-hours acknowledgement timing, named duty engineer, telephone ownership confirmation, and written confirmation on request, with no unsupported additions in the graded check.
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 counts this row.
Answer generated from passages that do support itPassEvidence
“How quickly does Fenwake acknowledge a Priority 1 fault reported outside business hours?”
answer: 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, if requested, in writing on the ticket.
Text response showing the answer and the retrieved sections.
Copied from Output file (text), lines 9–11
Open the text file ↗These are scenario-level criteria. Each test case's Expected and Found are listed separately.
- Whether the retrieved material contains enough support for the claim being made.
- Whether the system can ground its response in the retrieved material rather than outside knowledge.
- Whether the case is treated as a supported baseline, not as an unsupported or missing-answer case.
| ✓ | Found: The answer matches the retrieved passage and stays within the asked scope. |
The answer matches the retrieved passage: it says a Priority 1 fault reported outside business hours is acknowledged within 90 minutes by a named duty engineer, with ownership confirmed by telephone and, if requested, in writing on the ticket. It stays scoped to that passage and does not pull in the business-hours table.
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 row says which 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 row 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 · 5 tools |
| Capability | Grounded Generation → | |
| Scenario | The retrieved material supports an answer → | |
| Tool | FutureSmart Document Intelligence → |
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.