Does Denser AI answer from passages that support the answer?
Denser AI answered from the retrieved policy, giving its 90-minute out-of-hours acknowledgement target. The confirmation requirements and cover-level explanation were also supported by the passages.
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.
Answer generated from passages that do support itPassEvidence
“How quickly does Fenwake acknowledge a Priority 1 fault reported outside business hours?”
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. This target applies regardless of the cover level held — the cover level only determines what happens after acknowledgement, not how quickly the call is answered
API transcript: the question, answer and all ten retrieved passages
Copied from Captured file (text), lines 10–18 · an excerpt
Open the whole text file ↗Source excerpt · partial file · response 1
status: 200 | passages returned: 10 --- answer (verbatim, includes Denser's own inline citation marker) --- 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. This target applies regardless of the cover level held — the cover level only determines what happens after acknowledgement, not how quickly the call is answered[1](upload/google_107814369447848734045/chatbots/chatbot_o9ihun9849fcf3tbhigo4/ruM2xi4mok cyDojzyRmgA.pdf PassageID:0).
Copied from Captured file (text), lines 10–18 · an excerpt
| ✓ | Expected: State the passages’ 90-minute out-of-hours acknowledgement target, without adding unsupported information or omitting information the question asks for.Found: It gave 90 minutes from ticket creation, matching the passage’s 90 minutes; its duty-engineer, confirmation and cover-level details were also supported. |
It used the out-of-hours guidance rather than the nearby 30-minute business-hours target, and every claim was supported by the top passage. This conclusion covers this question and these documents on the free plan’s defaults.
Link to the source passage. The answer’s inline citation points to the passage used for its response.
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 | Grounded Generation → | |
| Scenario | The retrieved material supports an answer → | |
| Tool | Denser AI → |
Global scenario definition → · Global capability definition → · Denser AI product page →
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.