ML systems · BANKING77 · 2026

A small model.
A selective second opinion.

Keep confident predictions local. Ask the LLM when the specialist is unsure.

Source on GitHub ↗Evaluation evidence ↗

Three policies. One test set.

3,080 held-out cases
Accuracy / higher is better
Local specialist85.58%
Routed hybrid88.08%
LLM on every request92.18%
050100%

A shared 0 to 100% scale. The full LLM is more accurate; the hybrid uses fewer calls.

Requests sent to the LLM
Local answerLLM answer

Routed hybrid: 2,713 correct. 268 LLM requests. +2.50 accuracy points over the local specialist.

See exact values
Matched seed-11 results. Same 3,080 cases.
PolicyAccuracyCorrectLLM calls
Local only85.58%2,6360
Routed hybrid88.08%2,713268
LLM only92.18%2,8393,080

The route a request takes

EmbedFrozen MiniLM
ClassifyLogistic regression · 77 intents
Check confidenceFrozen threshold
2,812 local answers268 requests + 20 retrieved examples → LLM

The API charge tradeoff

Offline routing replay
Known usage-priced LLM charges
Routed hybrid$0.0514
LLM on every request$0.5763
$0$0.5763

91.1% lower known LLM charges.

With 4.09 percentage points less accuracy than the full LLM. This is an offline policy comparison, not measured production savings.

Method, accounting & limitations

One seed, one training pool, one public benchmark. The specialist used 1,540 training labels (20 per intent), plus 770 reused validation/development labels. Thresholds were frozen before test evaluation.

The study queried the LLM on all 3,080 cases. Routing counts describe an offline replay, not the fraction of calls purchased. Three attempts have unknown usage; invoice spend is unreconciled. Specialist hosting, retrieval, and production serving costs are excluded.

These results do not establish production reliability or generalization to other intent taxonomies.

All projects →