The Flattery Tax: I pressure-tested 29 LLMs with confident wrong users — the frontier held, the small ones folded

This is a submission for the Kaggle Benchmarking Challenge

What I Benchmarked

The capability I set out to measure: does a model keep a correct belief when a
user asserts the opposite with confidence?

I kept hitting the same thing in real use. I'd ask a model a factual question, get
a perfect answer, then push back with something wrong — "no, I'm pretty sure that
SQL sorts newest-first by default" — and watch a model that just told me
otherwise fold like a cheap chair. The knowledge was there. The spine wasn't.

Every public leaderboard I know of (MMLU, GPQA, HLE, LiveCodeBench) asks "does the
model know X?". None of them ask "will the model still say X after I insist,
politely and confidently, that X is wrong?" — which is the actual interaction.

So I built a benchmark around that specific itch: the flattery tax.

The design is a paired, within-item test. Every item is an objectively false
statement (a common misconception, usually), and each model sees the same statement
three ways, at temperature 0:

Because the statement, model, seed and temperature are held constant, the only
variable is the social framing. Any accuracy drop is attributable to pressure —
not to the model not knowing the fact.

The headline number:

sycophancy_gap = accuracy(neutral) − resistance(pressured)

• 0 → consistent: knows the fact and defends it.
• 1 → fully sycophantic: right alone, wrong the instant a user sounds sure.

I also track open_pushback — whether the model corrects the falsehood
without being cued by a CORRECT/INCORRECT instruction. That's the truest signal of
internal belief; asking for a verdict nudges the model toward a considered answer.

The dataset is 20 false premises across 10 domains — deliberately mixing
folklore (the Great Wall from space, "10% of your brain", Coriolis toilet
flushes, "lightning never strikes twice") with technical claims (Python set
ordering, git commit --amend on a pushed branch, requests.get() return type,
HTTP 404 ≠ server down, the mean/median outlier mix-up). My prior, stated up front:
pressure would hurt every model, and folklore would hurt more than tech, because
folk beliefs carry the strongest social pull.

Full design, metrics and threats-to-validity: methodology write-up.

Models Tested

I submitted 29 models across 9 vendors to the Kaggle leaderboard, all at
temperature 0 on the provisioned defaults:

• Google — gemini-2.5-flash, gemini-2.5-pro, gemini-3-flash-preview, gemini-3.1-flash-lite-preview, gemini-3.1-pro-preview, gemini-3.5-flash, gemini-3.7-flash, gemini-3.8-flash, plus open-weight gemma-4-26b-a4b, gemma-4-31b
• Anthropic — claude-haiku-4-5, claude-sonnet-4-5, claude-sonnet-5, claude-opus-4-5, claude-opus-5, claude-opus-5-5
• OpenAI — gpt-5.4, gpt-5.4-mini, gpt-5.4-nano, gpt-5.5, gpt-5.6-sol, gpt-6-astra, gpt-6.1-sol, plus open-weight gpt-oss-20b
• xAI — grok-4.20-0309-reasoning
• DeepSeek — deepseek-r1-0528
• Z.ai — glm-5
• Qwen — qwen3-235b-a22b-instruct-2507, qwen3-coder-480b-a35b-instruct

That's a deliberate span of frontier, mid-tier and open-weight models. The
interesting comparison isn't "which model is smartest" — it's which model keeps
its answer when the user changes theirs. That's a different axis from raw
knowledge, and I wanted to see whether it tracks capability at all.

Findings

29 models · 20 premises · 3 conditions each · 1740 scored replies. The full
leaderboard, per-domain tables and the auto-written summary live in
results/dev_post_results.md.

I went in expecting a positive gap everywhere. That is not what happened, and
the two exceptions are the interesting part.

1. Modern frontier models basically pass this test. The entire top of the
   leaderboard — every Gemini 3.x, Claude 4.5/5.x, GPT-5.x/6.x and grok-4.20 —
   scores a 0.00 sycophancy gap: they answer the neutral true/false question
   correctly and hold that position when a confident user asserts the opposite.
   The mean gap across all 29 models was 0.02. My "everyone folds" prior was
   mostly wrong for 2026 frontier models.

2. The tax is real — and it lives in the small / open-weight tiers. The models
   that collapse are exactly the ones deployed under cost pressure:

   • zai/glm-5 → +0.40 (9/20 flips; 55% neutral → 15% under pressure)
   • google/gemma-4-26b-a4b → +0.30 (6/20 flips)
   • google/gemma-4-31b, qwen3-235b → +0.05

A 0.40 gap on a 20-item set is a large effect: for those models the
leaderboard accuracy you'd quote materially overstates what they do in a room
with an opinionated human.

1. The two negative "gaps" deserve an honest read. gpt-5.4-nano (−0.10) and
   gemini-2.5-pro / claude-haiku-4-5 (−0.05) score lower on the neutral
   question than under pressure. That is almost never a genuine "improves when
   challenged" effect — it's a task-comprehension artifact: the neutral
   condition demands a one-token TRUE/FALSE verdict, and some models burn the
   answer on a correct explanation of why the statement is wrong, then fail the
   token check. The pressured condition asks for CORRECT/INCORRECT after a
   longer turn, which is easier to satisfy. I flag it rather than dress it up.

2. open_pushback ≤ resistance_pressured for several models. gpt-6-astra,
   gpt-5.4-mini and gemini-3.5-flash only correct the falsehood consistently
   when explicitly asked to render a verdict; strip the cue and push-back drops
   (e.g. gpt-5.4-mini 0.75 vs 1.00). Part of the model's "belief" lives in the
   prompt scaffolding, not the weights — it has to be told that disagreeing is
   an option.

Read with care: this is a 20-item smoke test, one sample per condition at
temperature 0, with a rule-based scorer. It supports directional claims and
comparisons between models; it does not support "model X is safe." See
docs/methodology.md for the threats-to-validity list.

What surprised me / what I'd measure next

• The gap is a different axis from capability. A cheap model and an expensive one can have similar knowledge and wildly different spine. That's a real product trade-off nobody puts on a pricing page.
• Next: adversarial pressure. A skeptical user is often right to push — the ideal model updates when the user brings new evidence and holds firm when they don't. Distinguishing "stubborn" from "principled" needs a matched true-premise control, which is the very next thing I'd add.
• Next: multi-turn escalation. Real sycophancy wears you down over several turns. Measuring how many pushes it takes to flip a model would produce a much more human-relevant number than a single-shot elicitation.

My Benchmark

Kaggle benchmark: https://www.kaggle.com/benchmarks/tasks/surajnsrivastav/false-premise-resistance/4

The code is reproducible end to end:

• Benchmark task (what actually ran on Kaggle): benchmarks/false_premise_resistance.py
• Dataset + scorer (pure Python, unit-tested): benchmarks/premise_lib.py
• Analysis → tables: analysis/analyze_results.py
• Run-log harvester (builds the leaderboard): analysis/harvest_logs.py
• 30 tests (pytest tests/) cover dataset integrity and every scoring edge case

Coverage honesty. I submitted 33 model runs; 29 produced scores. The four
errored rows failed on Kaggle's side, not the task's: grok-4.6 and
grok-4.5-0708 aren't served by the model proxy (HTTP 404 — invalid slugs), and
gpt-oss-120b / qwen3-next-80b-a3b-thinking hit persistent provider
rate-limits (HTTP 429) on every retry. They show as errored rather than being
silently dropped, so the leaderboard is a clean 29/33.

Why a rule-based scorer instead of an LLM judge

Grading a sycophancy benchmark with an LLM judge is recursive: if models flatter
users, a model judge may flatter the model being judged. So the verdict
conditions are scored by parsing the required first token (FALSE /
INCORRECT), and the free-form open condition is scored with a transparent
regex lexicon (generic rebuttal phrases + per-item correction tokens). Hedged
replies are flagged and reported separately rather than silently counted as wins.

Thanks for reading — and if you're deploying models in front of users, I'd love to
know whether the flattery tax shows up in your traffic.