Skip to content

Jev calibration

A System One model is only useful if its probabilities mean something: p = 0.9 should be right nine times in ten. TypeSafe publishes no ECE. Third-party numbers range from 0.037 to 0.246 depending on the suite. Ours: 0.079 raw on typed-decisions, the best of any model before fitting, and 0.093 / 0.080 on the two Metatext runs.

Leads on ece (lower is better): Jev — 0.079 on typed-decisions
#ModelDecisionsBeats baselineECE raw → held-out fittedp50 / case
1JevTypeSafehosted0.72618/200.079→ 0.049405 ms†
2LAYA typed-decisionsConvai Innovations
fine-tuned on this suite
0.714→ 0.76218/200.161→ 0.0163.5 s†
3LAYAConvai Innovations0.3432/200.196→ 0.0203.2 s†
4Vonwfzyx0.4615/200.249→ 0.027597 ms
5GLiClass multilang ultraKnowledgator
correct payload, no prompt
0.3953/200.281→ 0.031672 ms
6GLiNER2 largeFastino0.4869/200.300→ 0.0293.8 s†
7GLiClass large v3.0Knowledgator
correct payload, no prompt
0.4467/200.315→ 0.093977 ms
8LAYA multilingualConvai Innovations0.3452/200.322→ 0.0731.2 s†
9GLiNER 2.5 baseFastino0.3983/200.415→ 0.0591.3 s†

Ranked by ece (lower is better). typed-decisions: LAYA's public benchmark: four workflows × 100 JSON states × five typed questions = 2,000 decisions. Synthetic; gold is a teacher distribution and the label is its argmax. Large enough to carry an ordering. Every model is zero-shot except LAYA typed-decisions, which was fine-tuned on this suite. Decisions is the task-weighted mean accuracy of the best configuration per model; ECE is the mean expected calibration error over tasks, and the arrow shows the held-out ECE after one temperature per primitive fitted on the other half. Latency is p50 per three-question customer-service case on four CPU cores (Jev: API round trip); † means taken from the benchmark run rather than a clean timing pass. Updated September 2026.

Same ranking on the other suite: Metatext decisions.

Frequently asked questions

Is Jev well calibrated?

On our suites, yes, and better than every open model untuned (ECE 0.079 on 2,000 decisions). Independent suites disagree with each other: 0.037 on a 102-item task (Ben Greenberg), 0.121 on 150 passages (WotAI), 0.246 on Banking77 with permuted options (nibzard). Calibration is suite-dependent; measure it on your own traffic.

Can the open models be calibrated?

Yes, cheaply. One temperature per primitive, fitted on half the data and judged on the other half, takes GLiNER2 large from 0.300 to 0.029 and LAYA typed-decisions from 0.161 to 0.016. It does not move accuracy except for LAYA typed-decisions, which ships under-confident and gains 0.05.

Related