Skip to content

Extraction benchmark

Extraction is the fourth primitive and the one Jev does not have. Five labels (person, organization, location, date, money), eight cases, micro-F1. Not applicable is not zero: a model with no span head cannot be scored here.

Leads on extraction f1: GLiNER2 multi — 1.000 on Metatext decisions
#ModelDecisionsBeats baselineECE raw → held-out fittedp50 / caseExtraction F1
1GLiNER2 multiFastino0.4642/70.354202 ms†1.000
2GLiNER2 largeFastino0.7166/70.261627 ms†0.968
3GLiNER 2.5 baseFastino0.6435/70.251332 ms†0.968
4GLiNER2 baseFastino0.6313/70.350190 ms†0.935
5GLiNER 2.5 multiFastino0.4944/70.244346 ms†0.885
6GLiNER 2.5 smallFastino0.5744/70.172132 ms†0.812
7GLiGuard 300MFastino0.5373/70.230155 ms†0.000

Ranked by extraction f1. 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. Every model is zero-shot 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: typed-decisions.

Frequently asked questions

Can Jev extract entities?

No. Jev answers questions about text and never returns spans. If you need both decisions and extraction from one model, GLiNER2 is the only family measured here that does both.

Related