Can Vectorize.io trace an answer's claim to supporting source text?
Vectorize.io failed to give a citation that opened to text supporting the answer's claim. Both executions showed no citation pointer, so nothing could be opened against the claim.
1 of 1 test case failed
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.
Citation opened and read against the claim it supportsFailEvidence
“How quickly does Fenwake acknowledge a Priority 1 fault reported outside business hours?”
Fenwake acknowledges a Priority 1 fault reported outside business hours within 90 minutes. A named duty engineer will confirm ownership of the ticket by phone, and if requested, they can also provide written confirmation. This quick response is consistent across all cover levels, ensuring that urgent issues are addressed promptly, even when the service desk is not staffed. If you have any other questions or need more details, feel free to ask!
Text log with answer and citation check
Copied from Captured file (text), line 17
Open the text file ↗| ✗ | Expected: The citation should open to text that supports the answer's claim, not only the same document or topic.Found: The answer's claim appeared, but neither execution supplied a citation pointer to supporting text. |
It needed a citation that opens to supporting text. Both executions showed no citation pointer, so nothing could be opened against the claim on the tested surface.
No citation pointer. Both executions showed no citation pointer.
Answer still complete. The answer supplied the requested timing and owner details, but still had no citation pointer.
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 | Citations → | |
| Scenario | A claim in the answer traced back to its source → | |
| Tool | Vectorize.io → |
Global scenario definition → · Global capability definition → · Vectorize.io 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.