AIToday
AI Safety & AlignmentZenn AI/MLPublished: Oct 31, 2026, 06:00 JST

Jev scores 60% vs home AI's 83%, but errs only below 74% confidence

Send on LINE
Jev scores 60% vs home AI's 83%, but errs only below 74% confidence

3 Key Points

  1. What happened

    Testing Jev, a home-built AI, and a prior AI on 602 emails, the author scored 35 disputed cases: the home AI hit 83%, Jev 60%, the prior AI 49%.

  2. Why it matters

    Jev's errors all came with lowered confidence, so a threshold could filter them out — while the higher-scoring home AI's mistakes slipped through bearing high confidence.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, every morning.

Context & Analysis

The test began with a suspicion rather than a benchmark. In an earlier piece, the author had tried to replicate Jev's approach on a home PC and watched it declare, with 96% confidence, that an email saying a transaction had completed meant no money moved. That kind of confident error is harder to catch than a plain mistake, because a system that filters only low-confidence answers will wave it straight through. Jev's developer claimed special training aligned the confidence numbers with reality; this experiment was the check.

The 602-email comparison produced a split verdict. On raw accuracy over the 35 disputed cases, the home-built AI won at 83% against Jev's 60%, and the prior production AI trailed at 49%. But the error patterns told a different story: Jev never made a mistake above 74% confidence, while the home AI's errors arrived stamped with 96%, 89%, and similar figures and persisted even when the review threshold was raised to 95%. The home AI also labeled 191 of 543 emails as 99%-or-more confident, leaving almost no room to separate good answers from bad.

A second lesson came from the labeling work itself. Deciding whether an order confirmation counts as "money moved" changed the ranking of all three AIs, suggesting much of the disagreement reflected an undefined question rather than model weakness. And rewriting the prior AI's prompt with more detailed rules backfired: false positives multiplied twelvefold while misses fell, with nine of the new false positives landing on examples explicitly marked as non-matching. The author's takeaway is to split instructions into small questions rather than piling on conditions.

FAQ
How much did it cost to run Jev on 602 emails?
About $0.041, or roughly 6 yen, for 602 emails — about $0.00007 per email. The median response time was 0.46 seconds, with output free since Jev writes no prose.
Why did the author hand-label 65 emails instead of relying on the AIs?
If all three AIs were wrong, comparing them would show no difference. So the author opened and read 65 emails — 35 where opinions split and 30 random ones — and decided the correct answer for each.
Did making the instructions more detailed improve the prior AI's performance?
No — it got worse. After adding four positive and seven negative examples, accuracy fell from 78% to 74%, and false positives rose from 1 to 12, including 9 cases explicitly listed as non-matching.
Send on LINE

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleOpenAI rebuilds Model Spec around five core values