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

swanOne

This detail uses the public, hash-checked v1.4.1 aggregate. Scores and ranks can change when a new release is published; the page preview remains name-only.

JevBench v1.4.1 score

—

Partial run, not ranked — No completed sealed v1.4 run; retained as an unranked historical row.

Shown, not ranked. The marked tick is Jev 1.13.0 (63.3).

Published axes

intelligence
—
calibration
—
speed
—
cost
—

Accuracy per tier, incl. sealed

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.

  • A: Jev 1.13.0 — Jev (TypeSafe, closed) · Score 63.3 (#1)
  • B: swanOne — Jev rebuild · Score — (partial run, not ranked)

The four score axes

Radar: the four score axes, two systemsThe four score axes, Jev 1.13.0 vs swanOne. Intelligence: 53.1 vs none (0); Calibration: 76.3 vs none (0); Speed: 83.3 vs none (0); Cost: 52.0 vs none (0).50100Intelligence53.1 · none (0)Calibration76.3 · none (0)Speed83.3 · none (0)Cost52.0 · none (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, Jev 1.13.0 vs swanOne. Easy: 100% vs 100%; Standard: 99% vs 97%; Judge: 95% vs 93%; Hard: 74% vs 76%; Sealed: 37% vs —.50100Easy100% · 100%Standard99% · 97%Judge95% · 93%Hard74% · 76%Sealed37%
Share correct per tier; Sealed = the 308 private decisions, aggregate only.

Hard tier by family (v1.2 topics)

Radar: hard tier by family (v1.2 topics), two systemsHard tier by family (v1.2 topics), Jev 1.13.0 vs swanOne. Adversarial: 100% vs 100%; Ambiguous: 79% vs 86%; Judge: 79% vs 73%; Long policy: 61% vs 74%; Multi-hop: 86% vs 83%; Probability: 80% vs 70%; Routing: 100% vs 100%; Temporal / numeric: 27% vs 43%; Trade-off: 92% vs 92%; Trap: 100% vs 94%.50100Adversarial100% · 100%Ambiguous79% · 86%Judge79% · 73%Long policy61% · 74%Multi-hop86% · 83%Probability80% · 70%Routing100% · 100%Temporal /numeric27% · 43%Trade-off92% · 92%Trap100% · 94%
Share correct within each family of the 47 v1.2 hard-tier decisions (public and held-out).

Sealed set by family

swanOne has no sealed family breakdown.

Radar: sealed set by family, two systemsSealed set by family, Jev 1.13.0 vs swanOne. Ambiguous / abstain: 30% vs —; Judge: 34% vs —; Long policy: 28% vs —; Multi-hop: 45% vs —; Paraphrase: 64% vs —; Probability: 50% vs —; Safety judge: 38% vs —; Temporal / numeric: 29% vs —; Trade-off: 38% vs —; Trap / adversarial: 42% vs —.50100Ambiguous /abstain30%Judge34%Long policy28%Multi-hop45%Paraphrase64%Probability50%Safety judge38%Temporal /numeric29%Trade-off38%Trap /adversarial42%
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
Patch/repository and Qwen/Mia component-specific terms recorded in RESULT.md
Cost evidence
estimated; the board’s row disclosure contains the published basis.
Endpoint condition
our GPU (lium.io H200 141 GB), local container endpoint; serial; raw T=1.0
Published source
https://github.com/swanOne

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