General VLM benchmark data pipeline

Build visual benchmarks that really test models.

A reusable pipeline for building controlled visual edits, repairing local artifacts, authoring real-image probes, and evaluating whether VLMs can answer correctly when we test visual evidence.

Generate
Edit
Model Test
auto-check easy sample rejected hard case kept
Human Review
manual verification box annotation image repair
VLM Benchmark

SABRE: Scalable and Automated Benchmarking of VLMs under Stress

Zixuan Lan1* · Luzhe Sun2* · Matthew R. Walter2 · Jiawei Zhou3

University of Chicago1 · Toyota Technological Institute at Chicago2 · Stony Brook University3

Abstract

Vision-language models (VLMs) are improving rapidly, but benchmark development lags behind, making weaknesses hard to identify. Building stress tests is costly: samples must satisfy controlled conditions, remain answerable, and challenge current models. We present SABRE, a scalable, automated pipeline that converts a Test Primer (a Markdown Task Design with Data Schema) into structured specifications, generated or edited images, and question–answer pairs. Automated filtering removes candidates solved by a Filtering VLM, while human review verifies candidate validity and supports annotation correction and localized image repair. We instantiate SABRE-Prior to test whether VLMs follow visual evidence instead of relying on world priors—learned expectations about familiar objects and scenes. Its 600 images and 1,000 questions span Context (unexpected entities in familiar scenes), Texture (counterfactual materials), Attribute (non-canonical component counts), and Language Elicitation (answers suggested by language but unsupported by the image). Across six VLMs, macro-average accuracy ranges from 17.8% to 31.3% (22.6% mean). A real-image Attribute control is comparably difficult for the Filtering VLM. SABRE-Counting and SABRE-Spatial pilots show that the workflow supports other stress-test settings. These results establish SABRE as a reusable framework for constructing and refreshing VLM stress tests rather than a single fixed benchmark.

SABRE in Action

From automated benchmark construction to human verification and localized image repair.

01

Workflow Overview

From a Test Primer to structured candidates, automated filtering, and human-verified VLM stress tests.

SABRE workflow From Test Primer to verified stress test
Scalable · Automated
02

Annotation & Verification

Review paired images, mark visual regions, correct question–answer metadata, and save verified samples.

03

Entity Removal

Remove a localized entity while preserving the surrounding scene, structure, and visual consistency.

Try entity removal
04

Entity Swap

Replace a selected entity while retaining its location, scale, and relationship to the surrounding context.

Try entity swap
SABRE-Prior results

Performance under stress

Accuracy across four stress-test categories, with macro averages and 95% confidence intervals.

Accuracy of six vision-language models on SABRE-Prior Context, Texture, Attribute, and Language subsets, plus the macro average.
Rank Model Context Texture Attribute Language Macro avg.
01 Claude 4.6
10
40
17
58
31.3
02 Kimi-k2.6
7
52
17
17
23.3
03 Qwen 3.5
3
46
14
29
23.0
04 Gemini 3.5
0
52
26
11
22.3
05 GPT-5.4
1
28
20
23
18.0
06 Grok-4.3
4
28
16
23
17.8

Higher is better. Bold colored values mark the best result in each category.

Browser repair demo

Try localized image repair.

Local image · your Gemini key

Your image is never uploaded to SABRE. It stays in this browser and is sent directly to Gemini only when you run an edit.

BeforeDrag to mark the edit region
Choose an image to begin Nothing is uploaded to SABRE
No region selected
AfterGemini output · locally composited
Your repaired image appears here Run an edit after selecting a region
Bring your own key

Connect Gemini for this tab

Your key is used only for direct requests from this browser to Google. SABRE does not store it, and refreshing this page clears it.

Get a key in Google AI Studio ↗
For a public research demo, use a temporary or quota-restricted key. Google recommends keeping production API keys server-side.