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

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.

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.

Citation opened and read against the claim it supportsFailEvidence
What we sent

“How quickly does Fenwake acknowledge a Priority 1 fault reported outside business hours?”

What the tool returned
Text
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 vs. Found
✗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.
Supporting proof
Proof 1Screenshot
Notebook screenshot with answer and citation check
Open original ↗
Why this result

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.

Also observed in this test case

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.

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
A multi-page source was needed so a page pointer would matter; the question was asked on the answer surface, then the reply, citations, and citation targets were captured and opened.
Prompt template
default; no override
Retrieval settings
none set (the product's defaults)
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.

LevelNameScope
BenchmarkManaged RAG →15 scenarios · 9 tools
CapabilityCitations →
ScenarioA claim in the answer traced back to its source →
ToolVectorize.io →

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
13 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/a-claim-in-the-answer-traced-back-to-its-source · 0 pass · 1 fail · coverage 1/1 · graded 2026-10-16

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 · 2 KB
Proof 1 · Screenshot ↗image/png · 152 KB
File fingerprints (SHA-256)

A fingerprint identifies the exact file used for this result.

Captured file (text)e024e1161c2b3a7872ee915817d6321df54b47397748326555aef8f2714605c0
Proof 1 · Screenshotaba560e9a81d956567d1c937c3c49974eeed323bb805badb8f104b68b400c905