AI
Edward Ilin10 min read
Your client is about to publish advice that readers can disprove in thirty seconds. Stanford researchers re-tested 50 widely cited claims about language model behavior and found that 44 percent have expired.
Picture a thought leadership post warning that an AI tool "can't count" going live after the model changed.
Studies about language models describe particular models at a particular moment. Your client deliverables often treat them as permanent truths.
Stanford researchers Owen Queen and James Zou took 50 widely cited claims about large language models and tested them against 20 models from eight developers, as The Decoder reported. The models were released between July 2024 and September 2026. The result: 44 percent of the claims have expired, according to the Stanford team's own write-up.
The full breakdown is more useful than the headline number:
Among the 22 findings that came with an estimated expiration date, the average lifespan was 15.7 months. The Decoder's account adds that 16 percent had expired after one year, and 39 percent after two.
The research pipeline is slower than the release pipeline. Whatever you cite today was measured on yesterday's models. A paper that looked authoritative last spring may already be describing a model nobody uses.
Skill gaps close. Behavioral habits tend to persist.
Claims about what models cannot do expire fastest. According to The Decoder's summary of the study, five of nine reasoning-related findings are considered expired, and none of the nine have held up or grown stronger.
The expired list includes weaknesses that circulate constantly in marketing and explainer content:
The researchers suspect these errors have a clear "correct" outcome, which gives developers an obvious target to train toward. If your client's blog still uses "AI can't count letters" as a punchy example, it is now a liability.
The survivors tell the opposite story. Of the 11 findings that held or strengthened, three involve models acting as evaluators: they favor their own answers, rate accepted and rejected papers similarly, and are swayed by linguistic spin in medical abstracts. Three more involve sycophancy toward users. The study also lists a left-leaning political bias, near-identical answers to open-ended questions, and uneven random number generation.
A generic statement about "AI" is almost always unsafe. A dated statement about a named model is usually fine. Queen and Zou make the same point in their conclusion. Findings should be framed as observations about specific models at a specific time, with the model, version and date documented.
The Stanford authors also warn against reading the study as permission to say models have no problems. On two-hop questions, where a model must combine two facts it knows individually, Claude Sonnet 5.5 still fails in about 10 percent of cases where it answers both single questions correctly. The original paper reported 43 percent for ChatGPT.
The weakness shrank, but it didn't vanish.
The citation test shows how uneven the picture is. In the original 2023 study by Walters and Wilder, GPT-3.5 invented 55 percent of its references. Re-run on current models, GPT-6.1 Sol fabricated 0 percent and Claude Sonnet 5.5 came in at 1 percent.
Yet Qwen3.7-Flash, also a 2026 model, still fabricated 69 percent in the same test.
Even inside one release window, the spread is wide. Among models released between July and September 2026, expired findings range from 11 for DeepSeek V4 Pro to 30 for GPT-6.1 Sol. The study says release date, provider and model size don't reliably predict the pattern.
Would your own copy survive that test? If a draft says "LLMs struggle with X," ask which model, tested when, by whom. If nobody can answer, cut the sentence or rewrite it as a hedged, dated observation.
You don't need a research team. You need a short routine you can run between client calls.
1. Build "verify model claims" into the brief, not the final proofread. If your team produces high volumes across many channels, Brainpercent's brand voice and brief tools can hold that standing rule so every generated draft carries it from the first line.
2. Keep one shared sheet of claims checked. Log each claim with the date and the model.
3. Re-test the oldest rows first next quarter.
Do this once and you stop treating model research as a source of permanent facts. You treat it as a dated snapshot, which is what the evidence says it is.
Anchor it to a test you can point to. Instead of "AI makes up sources," write something like: "In our check on [model name, version] on [date], the tool listed references that did not exist." That sentence stays true even after the model changes, because it describes a past observation and not a permanent trait. Readers also trust it more, since it sounds like something a person actually did.
Keep a simple template in your style guide: model, version, date, what you tried, what happened. When a client pushes back with "can't we just say AI is unreliable?", show them the template next to a vague line and ask which one they would defend in a call with their own customer. The dated version usually wins that argument in under a minute.
Offer a swap before you argue. A line about models flattering users or favoring their own answers will age better than a line about arithmetic. Pitch it as an upgrade: same punchy tone, lower risk of a reader pasting the prompt into a chatbot and proving the post wrong.
If they still want the original, run the prompt in front of them on the model their audience most likely uses and send the screenshot. A failed example gets cut by the client themselves. A passed example tells you the line is already dead. Either way you have a record, and the decision stops being your opinion against theirs.
Match the schedule to the risk. Skill-gap claims (counting, arithmetic, long-context recall) deserve a quick look every quarter, since the study found that category goes stale fastest. Claims about model habits can wait longer, but not forever. A shared sheet that logs the claim, the model, and the last test date lets you sort by oldest and work from the top of the list.
You do not have to review everything at once. Tie the re-check to work you already do: when a post gets a refresh, a repost, or gets quoted in a new deck, test its claim first. That way the audit rides along with existing deadlines instead of becoming one more standing task you never have time for.
Check three things before it goes into copy: which models were tested, when the testing happened, and whether the paper says anything about how long the result should hold. Plenty of papers test one family of models at one moment and then write conclusions in general language. Sebastian Raschka's list of 2026 LLM research papers shows how many new models, training methods and reasoning approaches arrive within just a few months, which gives you a feel for how quickly a tested model can be replaced.
A paper about a model your client's audience no longer uses is background reading, not a citation. If you cannot tell which model was tested, treat the finding as a lead to verify yourself, and keep it out of client copy until you have run the check.
No. Honest limitation content is still some of the most useful material a client can publish, and readers are tired of hype. The point is to write it so it holds up. A post that says "here is what we tested, on which tool, and what we saw" gives readers something they can repeat on their own, which builds more credibility than a sweeping warning ever could.
A practical split helps when you plan the editorial calendar: use dated, tested observations for specific weaknesses, and use durable themes (human review, source checking, keeping a person accountable for the final copy) for the advice that should still make sense a year from now. The second group rarely needs a re-test, which frees your attention for the claims that do.
Pull your ten most-viewed client posts, flag every "AI can't" line, and re-test those prompts on today's models. Skill-gap lines go stale first, so those are your riskiest.
Every capability claim carries a named model, a version and a date.
Nothing here needs a research budget. It needs a rule your team applies before drafts reach a client.
To bake that rule into every draft from the first line, set up a brand voice and brief in Brainpercent.
Ready to automate all this? Brainpercent is the all-in-one content platform that generates SEO articles, social posts, and videos for you, on autopilot. Start your free trial or see pricing.
Posts, images and videos from your own site, in minutes.
Try it free