Decision model
GLiNER2.5-multi-Decide
1 question per request
20.2% of the 2,198 questions right (18.6% to 21.9%, 95% interval). Back to the leaderboard.
How we called it
- Kind
- Decision model
- Access
- GLiNER2 server, self-hosted
- Paid as
- Our own hardware
- Model ID
gliner2.5-multi-decide- Parameters
- 287M
- Hardware
- 1 × RTX PRO 6000 Blackwell (96 GB); FP16
- Note
- Fastino's decision fine-tune of GLiNER2.5 Multi
- Confidence from
- Option score
- Run
- 135, 7 October 2026
Settings
- Reasoning
- off
- Request format
- 1 question per request
- Requests at once
- 1
- Temperature
- not recorded
- Harness seed
- 0
- Harness commit
- not recorded
- Prompt version
- not recorded
Results
| Questions | Accuracy | 95% interval | Right |
|---|---|---|---|
| All questions | 20.2% | 18.6% to 21.9% | 444 of 2,198 |
| Reading | 21.0% | 18.1% to 24.3% | 138 of 656 |
| Grammar | 19.8% | 17.9% to 21.9% | 306 of 1,542 |
Comparison group: H. Compare with another setup.
Accuracy by topic
Confidence
- Answers kept at 99% or more
- 0, of which 0 wrong; 2,198 skipped, the model less than 99% sure
- Calibration gap
- 23.1 points
- AUROC, all questions
- 0.54 0.51 to 0.57
- AUROC, reading
- 0.56 0.51 to 0.61
- AUROC, grammar
- 0.53 0.49 to 0.57
- Brier score
- 0.233
- Accuracy of its surest answers
- most confident fifth: 23.4% right; most confident half: 21.6% right; most confident four fifths: 21.3% right
- Typical score of a right answer
- 40.7%
- Typical score of a wrong answer
- 38.5%
Repeats
We did not repeat this setup.
Latency
- Latency, median request
- 0.009 s (this run)
- Latency, 90th percentile
- 0.010 s
- Requests at once
- 1
- Throughput
- 6615.9 questions per minute of request time
- Request time
- 0.3 minutes, over the requests whose answers were kept
Latency: the time from sending one request to receiving its answer, measured from our computer, network and any retries within the request included. Request time: the time at least one request was in flight, over the requests whose answers were kept. It is not the run's elapsed time: it leaves out requests that failed and any pause before a run was resumed.
Cost
- $ per 1,000 questions
- Not measured
- Basis
- No dollar estimate; see hardware and time
- Input tokens per question
- 196
- Output tokens per question
- 0