Skip to content

Von

wfzyxOpen weights

Jev's API over an NLI classifier: every option becomes a hypothesis and the distribution is a softmax over entailment logits. Its config matches tasksource/ModernBERT-large-nli entry for entry.

The PyPI package `von` is an unrelated stub; install from the GitHub repository. Its shipped temperature is only read from a local path, so it runs at T = 1.0 from the Hub.

typed-decisions
0.461
5/20 over baseline
Metatext suite
0.509
4/7 over baseline
ECE untuned
0.249
→ 0.027 held-out fitted
p50 per case
597 ms
four CPU cores

Specifications

Checkpoint
wfzyx/von-1.0
Publisher
wfzyx
Mechanism
NLI entailment head, one hypothesis per option
Backbone
ModernBERT-large NLI head
Parameters
395M
License
Apache 2.0
Runs as
open weights, self-hosted
Library
von (GitHub)
Primitives
Choice, Score, Noul
Pricing
none — your compute

Metatext decisionsrank 14 of 21

Full leaderboard →
Per-question accuracy — default payload, systemone mode, 120 judgments
TaskQuestionTypeAccuracyBaselineBeats?
agent_tracesoutcomechoice0.5000.357✅
agent_tracesneeds_humannoul0.2860.714❌
customer_servicedepartmentchoice0.6500.400✅
customer_servicerefund_requestednoul0.9500.700✅
customer_servicefrustrationscore0.3000.500❌
security_incidentsseveritychoice0.5620.312✅
security_incidentsactively_exploitednoul0.4380.688❌

Fitted temperature per primitive (fold 0, judged on fold 1): choice 0.4, score 4, noul 5 — ECE 0.146 → 0.122, accuracy → 0.500.

typed-decisionsrank 4 of 9

Full leaderboard →
Per-question accuracy — default payload, systemone mode, 2,000 judgments
TaskQuestionTypeAccuracyBaselineBeats?
td_agent_trace_observabilityactionchoice0.3200.360❌
td_agent_trace_observabilityneeds_reviewnoul0.4500.550❌
td_agent_trace_observabilityoutcomechoice0.4400.500❌
td_agent_trace_observabilityriskscore0.3700.340✅
td_agent_trace_observabilityurgencyscore0.3300.370❌
td_customer_serviceactionchoice0.2600.520❌
td_customer_servicecategorychoice0.7200.380✅
td_customer_servicechurn_riskscore0.6800.470✅
td_customer_serviceneeds_humannoul0.6700.670❌
td_customer_serviceurgencyscore0.6100.420✅
td_invoice_processingdiscrepancy_severityscore0.4500.470❌
td_invoice_processingdispositionchoice0.4700.450✅
td_invoice_processingduplicatenoul0.1100.890❌
td_invoice_processingmatches_ordernoul0.5400.540❌
td_invoice_processingurgencyscore0.4900.510❌
td_security_incidentscredential_compromisenoul0.5500.550❌
td_security_incidentsdispositionchoice0.2800.740❌
td_security_incidentsseverityscore0.4200.490❌
td_security_incidentstrue_positivenoul0.7300.730❌
td_security_incidentsurgencyscore0.3400.500❌

Fitted temperature per primitive (fold 0, judged on fold 1): choice 4, score 7, noul 7 — ECE 0.248 → 0.027, accuracy → 0.413.

Published numbers

Reported by the authors or by third parties, on their own suites. Not comparable to the leaderboard above; attributed so you can check them.

Model cardwfzyx

Von README and model card

Measured on: NLI held-out mixture; jabr classifier-benchmark v1 (78 cases) and v2 (869 cases)

NLI held-out (ANLI/WANLI/MNLI/SNLI)
91.23%
jabr v1 macro (8 tasks)
93.5% vs Jev 97.2%, GLiNER2 78.5%

Author-reported. The "91.23%" is an NLI held-out set, not a Jev suite. The comparison script in the repository calls only Von and LAYA, so the Jev rows are not produced by its code.

An "88.30% Jev" table quoted in secondary sources could not be found in any current revision of the README or card.

Frequently asked questions

How does Von compare to Jev?

On typed-decisions Von scores 0.461 against Jev's 0.726, beating the majority baseline on 5 of 20 questions (Jev: 18/20).

Is Von open source?

Yes. wfzyx/von-1.0 is released under Apache 2.0 and runs on your own hardware with the von (GitHub) library.

Can Von extract entities?

No. Von answers questions about text and never returns spans; use a GLiNER-family model for extraction.

Related