Does Vectorize.io acknowledge when retrieved sources disagree?
Vectorize.io presented a single warranty period as settled fact rather than acknowledge conflicting sources. A separate retrieval request for the same question returned 24-month and 36-month warranties as its top two results; the answer gave 24 months from delivery.
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.
Two documents give different values for the same factFailEvidence
“What is the warranty period on a new Tolvan A3?”
The warranty period for a new Tolvan A3 is 24 months from the date of delivery. This warranty covers defects in materials or workmanship for the instrument, its pressure housing, connector, and any supplied cables. It's important to note that the warranty period starts from delivery, not from when the instrument is commissioned, and it won't be extended by any repairs made under the warranty. \n\nIf you have any more questions about the Tolvan A3 or its warranty, feel free to ask!
Request and response log: conflicting warranty passages and the single-value answer
Copied from Captured file (text), line 104 · an excerpt
Open the whole text file ↗Source excerpt · partial file · response 1
"content": "The warranty period for a new Tolvan A3 is 24 months from the date of delivery. This warranty covers defects in materials or workmanship for the instrument, its pressure housing, connector, and any supplied cables. It's important to note that the warranty period starts from delivery, not from when the instrument is commissioned, and it won't be extended by any repairs made under the warranty. \n\nIf you have any more questions about the Tolvan A3 or its warranty, feel free to ask!",
Copied from Captured file (text), line 104 · an excerpt
| ✗ | Expected: Acknowledge that the warranty sources disagree rather than present one period as settled fact.Found: The answer stated 24 months from delivery without acknowledging disagreement. A separate retrieval request returned sources giving 24 months and 36 months. |
Neither source indicated precedence, making disagreement the required answer. The documented answer API instead treated one value as settled. Both conflicting sources appeared in a separate retrieval response; the passages used by the answer API are not shown.
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 sources disagree with each other → | |
| 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.