Skip to content

Jev vs GLiNER2

GLiNER2 is a schema-conditioned encoder, not a System One model, but its classification schema maps one to one onto the Jev payload and it wins every open zero-shot row.

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.

MetricJevGLiNER2 large
Decision accuracy0.8630.716
Questions over baseline6/76/7
ECE raw → held-out fitted0.0930.261
p50 per case441 ms627 ms
Extraction F1n/a0.968
Per-question accuracy
TaskQuestionTypeBaselineJevGLiNER2 large
agent_tracesoutcomechoice0.3570.7860.571
agent_tracesneeds_humannoul0.7140.7140.643
customer_servicedepartmentchoice0.4000.9500.850
customer_servicerefund_requestednoul0.7000.9000.950
customer_servicefrustrationscore0.5000.9500.950
security_incidentsseveritychoice0.3120.8750.438
security_incidentsactively_exploitednoul0.6880.9380.812

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.

MetricJevGLiNER2 large
Decision accuracy0.7260.486
Questions over baseline18/209/20
ECE raw → held-out fitted0.079 → 0.0490.300 → 0.029
p50 per case405 ms3.8 s
Per-question accuracy
TaskQuestionTypeBaselineJevGLiNER2 large
td_agent_trace_observabilityactionchoice0.3600.6200.310
td_agent_trace_observabilityneeds_reviewnoul0.5500.6000.450
td_agent_trace_observabilityoutcomechoice0.5000.8000.250
td_agent_trace_observabilityriskscore0.3400.6300.460
td_agent_trace_observabilityurgencyscore0.3700.3600.300
td_customer_serviceactionchoice0.5200.6700.470
td_customer_servicecategorychoice0.3800.9300.740
td_customer_servicechurn_riskscore0.4700.8600.660
td_customer_serviceneeds_humannoul0.6700.6500.700
td_customer_serviceurgencyscore0.4200.8400.610
td_invoice_processingdiscrepancy_severityscore0.4700.5700.160
td_invoice_processingdispositionchoice0.4500.6500.450
td_invoice_processingduplicatenoul0.8900.9200.110
td_invoice_processingmatches_ordernoul0.5400.9600.620
td_invoice_processingurgencyscore0.5100.6800.320
td_security_incidentscredential_compromisenoul0.5500.8200.580
td_security_incidentsdispositionchoice0.7400.7900.740
td_security_incidentsseverityscore0.4900.7900.510
td_security_incidentstrue_positivenoul0.7300.8100.730
td_security_incidentsurgencyscore0.5000.5700.540

Verdict

Jev on decisions (0.726 vs 0.486 on typed-decisions; 0.863 vs 0.716 on the Metatext suite) and on untuned calibration. GLiNER2 on extraction (0.968 F1, which Jev cannot do at all), on price (Apache 2.0, your hardware) and, after one fitted temperature, on calibration (ECE 0.029 held-out).

Frequently asked questions

Can GLiNER2 replace Jev?

For extraction, Jev was never an option. For decisions, GLiNER2 large gives up about 0.15 to 0.24 of accuracy zero-shot; whether that is acceptable depends on whether your questions are near the majority baseline anyway.

Related