Benchmark archive

Split by who ran it, then grouped by task. Results from different datasets and protocols are never averaged, ranked against each other, or reduced to a single score.

Two provenance classes, never pooled
RUN records are ones JevBench executed. E records are evidence we collected from someone else, with its source attached. A run we executed carries no evidence tier, because the A–D scale grades independence from the party with an interest in the result and on our own runs that party is us. The two classes are never combined into one ranking — see the methodology.
Run by JevBench
RUN 001

Banking77 intent classification — complete test split

BANKING77 (complete official test split) · n = 3,080 · 2026-09-20 · JevBench

JBFirst-party · run by JevBench
80.3%
Jev · jev-1.13.0
7 limitations→
RUN 003

Ad Detector on SMS and YouTube comments (VE-001)

VE-001 AI-adjudicated subset of two UCI spam corpora · n = 200 · 2026-09-23 · JevBench

JBFirst-party · run by JevBench
94.0%
Jev · jev-1.13.0
7 limitations→
RUN 005

Chinese versus English virtual-assistant intent on MASSIVE (VE-002)

MASSIVE 1.1 test split, paired en-US and zh-CN · n = 2,974 · 2026-09-25 · JevBench · pre-registered

JBFirst-party · run by JevBench
79.3%
Jev · jev-1.13.0
7 limitations→
RUN 006

Next-step element selection on Mind2Web (VE-003)

Mind2Web test splits (cross-task, cross-website, cross-domain) · n = 9,378 · 2026-09-26 · JevBench · pre-registered

JBFirst-party · run by JevBench
38.4%
Jev · jev-1.13.0
7 limitations→
RUN 007

Page context and candidate count for next-step selection on Mind2Web (VE-004)

Mind2Web test splits (cross-task, cross-website, cross-domain) · n = 9,378 · 2026-09-26 · JevBench · pre-registered

JBFirst-party · run by JevBench
42.3%
Jev · jev-1.13.0
7 limitations→
RUN 008

Jev versus a free open model on MASSIVE intent (VE-005)

MASSIVE 1.1 test split, paired en-US and zh-CN · n = 2,974 · 2026-09-27 · JevBench · pre-registered

JBFirst-party · run by JevBench
81.7%
Jev · jev-1.13.0
48.3%
BGE-M3, zero-shot · BAAI/bge-m3@5617a9f
88.1%
BGE-M3 + logistic regression · BAAI/bge-m3@5617a9f + logistic regression (C=10)
6 limitations→
RUN 009

Jev against OpenDecider, Laya and open-jev on MASSIVE intent (VE-006)

MASSIVE 1.1 test split, paired en-US and zh-CN · n = 2,974 · 2026-10-02 · JevBench · pre-registered

JBFirst-party · run by JevBench
81.7%
Jev · jev-1.13.0
54.4%
OpenDecider-nano · manjunathshiva/opendecider-nano@6ac21e9
52.9%
open-jev (DeBERTa-v3-large) · com-kotobalabs/open-jev-deberta-v3-large@188ee67
43.9%
Laya-multilingual · convaiinnovations/laya (multilingual)@55cf4c4
37.3%
Laya (English checkpoint) · convaiinnovations/laya@55cf4c4
7 limitations→
Analyses and repeats of those runs

An analysis re-reads decisions already recorded above and asks a different question of them. A repeat sends a run’s inputs again to check that its answers hold. Neither is counted as a separate run.

RUN 002 · offline analysis of RUN 001 · 0 new API calls

Can Jev know when it is wrong?

Selective prediction on the same 3,080 decisions: error-detection AUROC, the coverage available at a 95% quality bar, and the errors returned at maximum confidence that no threshold can reach.

→
RUN 004 · repeat of RUN 003 · 400 new API calls

Does Jev give the same answer twice?

RUN 003’s 200 texts sent twice more: 2 labels changed, and its “no errors kept at 0.70” held in 1 of 3 runs.

→
Collected evidence · Security detection
Collected evidence · Classification
Collected evidence · Intent & routing
Collected evidence · Agent tool-call risk
Collected evidence · Agent workloads
Direct comparisons

A comparison page exists only where a single run measured both models on the same data under the same protocol, and both sides have verified pricing. No head-to-head, no page.

Jev vs BGE-M3, zero-shot — pending pricingJev vs BGE-M3 + logistic regression — pending pricingJev vs OpenDecider-nano — pending pricingJev vs open-jev (DeBERTa-v3-large) — pending pricingJev vs Laya-multilingual — pending pricingJev vs Laya (English checkpoint) — pending pricingJev vs Claude Haiku 4.5 →Jev vs GPT-5.4 nano — pending pricingJev vs GPT-5.6 Terra — pending pricingJev vs BGE-small-en-v1.5 + logistic regression — pending pricingJev vs TF-IDF + logistic regression — pending pricingJev vs Jev + TF-IDF ensemble — pending pricingJev vs Qwen 3.8 27B — pending pricingJev vs Needle 3 — pending pricing
Evidence tiers
A
Independent · Reproduction artifacts available

Run by a third party with no vendor involvement. Code and dataset or protocol are public, so the result could be re-run. This does not mean anyone has re-run it — see `independentlyReproduced`, which nothing in the dataset sets yet.

12 runs
B
Independent · Published

Run by a third-party researcher or outlet, but reproduction material is partial or absent.

0 runs
C
Vendor-reported

Published by the vendor of the model being measured. Recorded for completeness, never treated as independent evidence.

0 runs
D
Anecdotal

A single hands-on session, blog post or social media report. Directional only.

0 runs
JB
First-party · run by JevBench

Not a tier and not a grade. These runs sit outside the A–D scale because that scale measures independence from the party with an interest in the result, and here that party is JevBench. Full artifacts are published so the figures can be recomputed rather than trusted.

7 runs

Tiers grade provenance, not result strength. A small study can be tier A; its size is recorded in the run’s sample count and limitations, not in its tier. Tier A means the artifacts to re-run a benchmark are public — it does not mean anyone has re-run it, and nothing in this dataset has been independently reproduced.