Skip to content

Jev vs Von

Von presents every option as a hypothesis and softmaxes the entailment logits. It is the cleanest test of whether Jev's advantage is its mechanism: an NLI head is the obvious way to build one.

Metatext decisions

Three hand-written workflows (support tickets, security incidents, agent traces), seven questions, about 123 judgments per model. Small, so treat a ±0.1 difference as a tie; every question has a majority baseline the model has to beat.

MetricJevVon
Decision accuracy0.8630.509
Questions over baseline6/74/7
ECE raw → held-out fitted0.0930.234 → 0.122
p50 per case441 ms597 ms
Extraction F1n/an/a
Per-question accuracy
TaskQuestionTypeBaselineJevVon
agent_tracesoutcomechoice0.3570.7860.500
agent_tracesneeds_humannoul0.7140.7140.286
customer_servicedepartmentchoice0.4000.9500.650
customer_servicerefund_requestednoul0.7000.9000.950
customer_servicefrustrationscore0.5000.9500.300
security_incidentsseveritychoice0.3120.8750.562
security_incidentsactively_exploitednoul0.6880.9380.438

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.

MetricJevVon
Decision accuracy0.7260.461
Questions over baseline18/205/20
ECE raw → held-out fitted0.079 → 0.0490.249 → 0.027
p50 per case405 ms597 ms
Per-question accuracy
TaskQuestionTypeBaselineJevVon
td_agent_trace_observabilityactionchoice0.3600.6200.320
td_agent_trace_observabilityneeds_reviewnoul0.5500.6000.450
td_agent_trace_observabilityoutcomechoice0.5000.8000.440
td_agent_trace_observabilityriskscore0.3400.6300.370
td_agent_trace_observabilityurgencyscore0.3700.3600.330
td_customer_serviceactionchoice0.5200.6700.260
td_customer_servicecategorychoice0.3800.9300.720
td_customer_servicechurn_riskscore0.4700.8600.680
td_customer_serviceneeds_humannoul0.6700.6500.670
td_customer_serviceurgencyscore0.4200.8400.610
td_invoice_processingdiscrepancy_severityscore0.4700.5700.450
td_invoice_processingdispositionchoice0.4500.6500.470
td_invoice_processingduplicatenoul0.8900.9200.110
td_invoice_processingmatches_ordernoul0.5400.9600.540
td_invoice_processingurgencyscore0.5100.6800.490
td_security_incidentscredential_compromisenoul0.5500.8200.550
td_security_incidentsdispositionchoice0.7400.7900.280
td_security_incidentsseverityscore0.4900.7900.420
td_security_incidentstrue_positivenoul0.7300.8100.730
td_security_incidentsurgencyscore0.5000.5700.340

Verdict

Jev by 0.35 on the Metatext suite and 0.27 on typed-decisions. Von lands level with the GLiClass row that uses the same NLI mapping, which says the borrowed NLI head is doing the work, and it fails Score, like every NLI-mapped row. Its README's comparison table is not produced by anything in its repository.

Frequently asked questions

Is Von's "91.23%" a Jev benchmark?

No. It is Von's held-out NLI mixture (ANLI, WANLI, MNLI, SNLI). On a shared decision suite (jabr v2) its own card has Jev at 96.6% and Von at 72.0%.

Related