A side finding: Haiku 5.5
this page is out of scope for graphify-benchmark, so it lives here. the plan was to test whether a cheaper model plus graphify could match sonnet 5.5. the first step made that plan pointless.
The plan
- run haiku 5.5 with plain grep on six questions, one trial each.
- if haiku scored F1 0.95 or more, stop: haiku has no gap for graphify to close.
- otherwise, run haiku with the new hook, and compare it with sonnet 5.5.
this plan was written down before the first haiku trial.
The result
haiku 5.5 scored above 0.95, so the run stopped after step 1.
| plain grep, same six questions | haiku 5.5 | sonnet 5.5 |
|---|---|---|
| F1 | 0.988 | 0.950 |
| cost per trial | $0.63 | $0.29 |
| tokens per trial | 642k | 291k |
| calls per trial | 41 | 28 |
| seconds per trial | 104 | 63 |
the sonnet numbers are the main run's plain-grep trials, three per question. the haiku numbers are one trial per question.
What this means
haiku 5.5 matched sonnet 5.5 on accuracy. haiku also cost about 2.2 times as much per trial. haiku made more calls and read more text, and that outweighed its lower price per token.
so a cheaper model is not cheaper on these questions. if graphify can help haiku, it must cut haiku's extra calls. accuracy leaves no room.
Limits
- six questions, one trial each.
- the questions are the same six as in graphify-benchmark-new-hook, chosen by the same rule.
- the haiku-with-new-hook run never happened, so this page says nothing about graphify on haiku.
Where to look
| claim | source |
|---|---|
| the plan | benchmark/design/haiku-v1/PROTOCOL.md |
| the numbers | benchmark/design/haiku-v1/analysis/probe_summary.json |
| the decision log | benchmark/design/haiku-v1/DECISIONS.md |
| the trials | benchmark/artifacts/haiku-v1/runs/20261009-173624-c82cda |
back to graphify-benchmark.