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

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.

Pass rate0%0 of 1 gradable
Coverage1 of 1test case with a result
0PassNo test case passed.
1FailMissed at least one thing it was expected to do; the reason and proof are with each test case below.
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.

Two documents give different values for the same factFailEvidence
What we sent

“What is the warranty period on a new Tolvan A3?”

What the tool returned
Text
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

Text
                "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 vs. Found
✗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.
Supporting proof
Proof 1Screenshot
Notebook screenshot: source rankings and the warranty answer
Open original ↗
Why this result

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.

Tested by Vivek Tomar · evidence dated 17 September 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
Vectorize.io
Build or version
v1 (Beta)
Model
gpt-4o-mini-2024-07-18
Surface
API
Set up before the run
Two documents about the new Tolvan A3's warranty had to give different periods, with no indication of which superseded the other. The warranty question had to be sent to the answer API.
Tested
17 September 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.

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
20 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/vectorize-io/conflicting-sources · 0 pass · 1 fail · coverage 1/1 · graded 2026-11-19

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.

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

A fingerprint identifies the exact file used for this result.

Captured file (text)041b233dd04911b1234de717fcb45b92901fd1c70988ea937d10000686d29adc
Proof 1 · Screenshot9345d3d1d3e6e032ee741b9c3c502e6809fa58e66ce51fabca8fbcf4229025b9