Benchmarks
More
OverviewBenchmaxxingCompareChartsCost vs CapabilityProviders per ModelProvider explorerGatewaysEU & SovereignJev-class modelsImage JevBenchAbout
JevBench by Benchmark Heaven · v1.4.2.2 · individual system

open-jev-deberta-v3-large (local CPU)

Jev rebuild · by Kotoba Labs

JevBench v1.4.2.2 score

12.6

Rank #73 of 91 ranked systems.

50.6 points behind Jev 1.13.0's 63.3.

Where it sits among the 91 ranked systems. The marked tick is Jev 1.13.0 (63.3).

Published axes

intelligence
25.6
calibration
66.6
speed
66.0
cost
74.0

Against Jev 1.13.0

Four radars compare this fixed pair across the score axes, accuracy per tier, and accuracy by family on the hard tier and sealed set. Further out is better on every spoke.

The four score axes

Radar: the four score axes, two systemsThe four score axes, open-jev-deberta-v3-large vs Jev 1.13.0. Intelligence: 25.6 vs 53.1; Calibration: 66.6 vs 76.3; Speed: 66.0 vs 83.3; Cost: 74.0 vs 52.0.50100Intelligence25.6 · 53.1Calibration66.6 · 76.3Speed66.0 · 83.3Cost74.0 · 52.0
0–100, the values in the table. A label-only system has no calibration (counted as 0).

Accuracy per tier, incl. sealed

Radar: accuracy per tier, incl. sealed, two systemsAccuracy per tier, incl. sealed, open-jev-deberta-v3-large vs Jev 1.13.0. Easy: 100% vs 100%; Standard: 49% vs 99%; Judge: 53% vs 95%; Hard: 36% vs 74%; Sealed: 30% vs 37%.50100Easy100% · 100%Standard49% · 99%Judge53% · 95%Hard36% · 74%Sealed30% · 37%
Share correct per tier; Sealed = the 308 private decisions, aggregate only.

Current question set by family (hard + sealed)

Radar: current question set by family (hard + sealed), two systemsCurrent question set by family (hard + sealed), open-jev-deberta-v3-large vs Jev 1.13.0. Ambiguous / abstain: 39% vs 43%; Judge: 49% vs 54%; Long policy: 32% vs 44%; Multi-hop: 32% vs 64%; Probability: 21% vs 63%; Temporal / numeric: 20% vs 28%; Trade-off: 32% vs 55%; Routing: 20% vs 100%; Trap / adversarial: 43% vs 83%; Paraphrase: 14% vs 64%; Safety judge: 44% vs 38%.50100Ambiguous /abstain39% · 43%Judge49% · 54%Long policy32% · 44%Multi-hop32% · 64%Probability21% · 63%Temporal /numeric20% · 28%Trade-off32% · 55%Routing20% · 100%Trap /adversarial43% · 83%Paraphrase14% · 64%Safety judge44% · 38%
Share correct per family across the 220 hard-tier decisions (public and held out) and the 308 sealed decisions of v1.4, pooled; Routing is hard-tier only, Paraphrase and Safety judge sealed only.

Sealed set by family

Radar: sealed set by family, two systemsSealed set by family, open-jev-deberta-v3-large vs Jev 1.13.0. Ambiguous / abstain: 38% vs 30%; Judge: 44% vs 34%; Long policy: 30% vs 28%; Multi-hop: 26% vs 45%; Paraphrase: 14% vs 64%; Probability: 14% vs 50%; Safety judge: 44% vs 38%; Temporal / numeric: 23% vs 29%; Trade-off: 27% vs 38%; Trap / adversarial: 33% vs 42%.50100Ambiguous /abstain38% · 30%Judge44% · 34%Long policy30% · 28%Multi-hop26% · 45%Paraphrase14% · 64%Probability14% · 50%Safety judge44% · 38%Temporal /numeric23% · 29%Trade-off27% · 38%Trap /adversarial33% · 42%
Share correct within each sealed family — system-level aggregates; the items stay private.

Availability and evidence

Openness
Code and weights marked open in the published row
License note
Apache-2.0 (model card); DeBERTa-v3 keeps its own terms
Cost evidence
estimated; the board’s row disclosure contains the published basis.
Endpoint condition
our CPU (2 threads, Ryzen 5 3600)
Note on this row
297/308 sealed items answered validly (failures count as wrong)
Published source
https://github.com/kotoba-lang/typed-decisions

From the public v1.4.2.2 aggregate. Scores and ranks can change when a new release is published.

Read the full board and published method. The overall score is a composite, not raw accuracy.