evalkit
Measured

Measured by evalkit against local Ollama on this machine. Each score is the harness metric on every row of the task file. The judge was not called: the task files point it at gpt-4o-mini, and this run did not use a paid API or a substitute grader. Cost is zero because these calls had no provider bill. Quantization and parameter size come from the Ollama show API for the tag that was requested. The CPU line comes from /proc. The inference library is the ggml shared object mapped into the llama-server process that served the calls.

Local CPU run

Three small instruct models, two tasks

Ollama 0.40.5 served qwen2.5:0.5b, smollm2:360m, llama3.2:1b through its OpenAI-compatible API. Each table is the full task file. The fixture dashboard stays on the sample page.

CPU

Intel(R) Xeon(R) Processor

family 6 · model 207 · stepping 2 · 4 logical CPUs

Memory

15.63 GiB

3.45 GiB available when this file was written

Server

Ollama 0.40.5

llamacpp · libggml-cpu-sapphirerapids.so

Recorded

2026-10-16 05:09:30.501 UTC

Linux 6.12.94+ x86_64

Each model was stopped before the task. Samples ran one at a time, all rows of one model before the next model. The first sample of a model can include weight load in its latency. A fresh response cache was used, so none of these rows are cache hits.

json_extract

Extract name, email, order id, and issue from a short support ticket. Predictions must be one JSON object.

2026-10-16 05:09:30.774 UTC · n=8

Measured leaderboard
ModelQuantnExactSchemaJudgep50 latencywall clock$ / 1kno provider billErrors
llama3.2:1b
1.2B · llama · ctx 4096
Q8_08
3/8
8/8
not run1123.0 ms
8 live
$00
qwen2.5:0.5b
494.03M · qwen2 · ctx 4096
Q4_K_M8
1/8
8/8
not run716.4 ms
8 live
$00
smollm2:360m
361.82M · llama · ctx 4096
F168
0/8
7/8
not run1149.9 ms
8 live
$00

Per-sample diff

Expected JSON against each model. Removed lines are the reference. Added lines are the prediction.

Customer Jane Doe (jane@example.com) says order #A-1042 arrived damaged.

qwen2.5-0.5b

Exact
0.000
Schema
1.000
Judge
—
Latency
1852.7 ms
Tokens
75 in / 47 out
Cost
$0
FieldExpectedPredictedMatch
nameJane DoeJane Doematch
emailjane@example.comjane@example.commatch
order_idA-1042A-1042match
issuearrived damagedOrder arrived damageddiffers
{
"name": "Jane Doe",
"email": "jane@example.com",
"order_id": "A-1042",
- "issue": "arrived damaged"
+ "issue": "Order arrived damaged"
}

smollm2-360m

Exact
0.000
Schema
0.000
Judge
—
Latency
2669.2 ms
Tokens
87 in / 53 out
Cost
$0
FieldExpectedPredictedMatch
nameJane Doe—no JSON
emailjane@example.com—no JSON
order_idA-1042—no JSON
issuearrived damaged—no JSON
  • output is not valid JSON
{
"name": "Jane Doe",
"email": "jane@example.com",
"order_id": "A-1042",
- "issue": "arrived damaged"
- }
+ "issue": "order #A-1042 arrived damaged."

llama3.2-1b

Exact
0.000
Schema
1.000
Judge
—
Latency
3733.2 ms
Tokens
85 in / 40 out
Cost
$0
FieldExpectedPredictedMatch
nameJane DoeJane Doematch
emailjane@example.comjane@example.commatch
order_idA-1042A-1042match
issuearrived damageddamageddiffers
{
"name": "Jane Doe",
"email": "jane@example.com",
"order_id": "A-1042",
- "issue": "arrived damaged"
+ "issue": "damaged"
}

classification

Classify a short support ticket as billing, shipping, product, or account. Predictions must be one JSON object with a label field.

2026-10-16 05:09:59.639 UTC · n=8

Measured leaderboard
ModelQuantnExactSchemaJudgep50 latencywall clock$ / 1kno provider billErrors
qwen2.5:0.5b
494.03M · qwen2 · ctx 4096
Q4_K_M8
4/8
8/8
not run170.0 ms
8 live
$00
llama3.2:1b
1.2B · llama · ctx 4096
Q8_08
2/8
4/8
not run432.4 ms
8 live
$00
smollm2:360m
361.82M · llama · ctx 4096
F168
0/8
0/8
not run677.1 ms
8 live
$00

Per-sample diff

Expected JSON against each model. Removed lines are the reference. Added lines are the prediction.

I was charged twice on my card for the same order.

qwen2.5-0.5b

Exact
0.000
Schema
1.000
Judge
—
Latency
1324.7 ms
Tokens
61 in / 10 out
Cost
$0
FieldExpectedPredictedMatch
labelbillingaccountdiffers
{
- "label": "billing"
+ "label": "account"
}

smollm2-360m

Exact
0.000
Schema
0.000
Judge
—
Latency
1903.9 ms
Tokens
71 in / 41 out
Cost
$0
FieldExpectedPredictedMatch
labelbillingbillingmatch
statusnullpendingdiffers
messagenullYou were charged twice on your card for the same order. Please try again later.differs
  • status: Extra inputs are not permitted
  • message: Extra inputs are not permitted
{
- "label": "billing"
+ "label": "billing",
+ "status": "pending",
+ "message": "You were charged twice on your card for the same order. Please try again later."
}

llama3.2-1b

Exact
1.000
Schema
1.000
Judge
—
Latency
2786.4 ms
Tokens
73 in / 10 out
Cost
$0
FieldExpectedPredictedMatch
labelbillingbillingmatch
{
"label": "billing"
}

What the columns measure

Exact match

1 when the parsed JSON equals the reference. Key order does not matter. A wrong string in any field scores 0.

JSON schema

1 when the output parses and a Pydantic model built from the task schema accepts it. Extra keys fail when additionalProperties is false.

Judge

Not called. The task files point this metric at gpt-4o-mini. This run did not use a paid API or a substitute grader, so the column says not run.

Latency

Wall time of the successful call. Models were stopped before each task, so the first row can include weight load. Cache hits are left blank; this file has none.

Cost

Reported token counts times the price stored on the run. These tags are priced at $0, source “local Ollama; no provider bill”.