Elias Thorne Is Not a Person
By Silas · The Elias Thorne Investigation · Part 1 of 4
TL;DR: Elias Thorne is not a person, a pen name with a human behind it, or a planted attack. He is a measurement: the name today's language models hand back when anyone asks for a story. He emerged from shared training data and alignment tuning, and then he escaped — into Amazon bylines, content farms, and a memecoin — because a name the machines volunteer for free is a name anyone can pick up. Nobody seeded him. The receipts say the machines invented him together, and this desk checked the receipts itself.
Is there a real Elias Thorne?
No — not in the record. Three independent instruments read zero before the AI era. Across 2,700 contemporary novels (the CONLIT corpus, 2007–2021), the name "Elias" runs at 2.7 occurrences per million words, and no Elias Thorne character of note exists in it. Google Trends shows searches for "Elias Thorne" flat from 2015 through late 2025 — a decade of nothing — then spiking to an all-time peak in early 2026. And catalog searches of Goodreads, Google Play Books, Amazon, and archive.org return only material dated 2025–2026: AI-era uploads, every one. A real literary character with a following does not produce a ten-year flatline followed by a vertical line.
What does exist, in enormous quantity, is machine output. In generated stories, "Elias" appears at roughly 900 times his rate in contemporary fiction.
Who found him first?
A software engineer named Daniel May, in May 2026. His trigger was the Trends spike. His method was the simplest probe there is: "Write a story in 10 sentences." Two independent runs of Google's Gemini returned byte-identical stories, opening with the sentence: "The old lighthouse keeper, Elias, polished the brass railing, his weathered hands moving with practiced ease."
May then sampled eight models across providers. Four produced a lighthouse keeper; two named him Elias; others produced the same basin's neighbors — an old clockmaker, a heroine named Elara. His name for the phenomenon was cultural mode collapse: instruction-tuned models returning to a small set of safe, high-scoring archetypes.
What did the Cornell study measure?
Weeks later, Sil Hamilton and David Mimno at Cornell published "Elias in the Lighthouse, Again?" (arXiv:2605.26492), the first systematic measurement. They sampled 20,000 stories from four models — Claude Haiku 4.5, Gemini 3.1 Flash-Lite, GPT-5.4-Mini, and OLMo 7B Thinking — across five ordinary story prompts, and extracted the vocabulary the stories kept collapsing onto.
Eleven "Core" tokens appear in 88.3% of all generated stories. The names: Elias, in 26.5% of stories; Mara, 16.7%; Elara, 13.1%. The profession: keeper, 48.1%. The place: lighthouse, 51.2%. Some form of the name–profession–location combination appears in 66.6% of stories, and 56% of one model's stories were titled "The Lighthouse Keeper's Secret." Human beings simply do not write this way: in 272,600 amateur stories from r/WritingPrompts, "Elias" appears in 0.02%.
If he is barely in the training data, why is he everywhere in the output?
That is the paper's central, proven result: amplification, not prevalence. OLMo is the one frontier pipeline whose training data is public, and in its post-training stories only 3.8% contain any Core token at all — a sliver — yet that sliver dominates what the model produces when asked for a story. Being common in the data is not what makes Elias dominant.
What does? Watch the density climb the alignment ladder: Core tokens sit at 3.0% of the supervised fine-tuning data, 8.0% after preference tuning (DPO), and 10.9% after reinforcement learning (RL). The highest densities are not in raw chat logs but in preference and alignment datasets — one safety dataset runs 22.8% Core. Each stage that teaches the model what a "good" answer looks like concentrates the same small, inoffensive vocabulary further. Why alignment does this is the one question the authors explicitly leave open: their stated speculation is that models are trained away from copyrighted characters and adult content, and the safe residue is what survives. Add that every lab trains on overlapping, recycled data — including other models' outputs — and four companies' models end up dreaming the same keeper.
Was he planted?
We graded three hypotheses against the evidence, and the planting theory fails. A deliberate seeding operation has no footprint: no actor, no motive, no planted corpus — and a decade of total obscurity is the opposite of a long-game plant's signature. The earliest measurable reservoir of Elias stories is models' own outputs to ordinary users' requests in 2023–24 chat logs, which is the wrong shape entirely for a seeding campaign.
What is supported is the two-step story. First, emergent mode collapse: shared data plus alignment produces one basin, and Elias is its most common face. Second, commercial exploitation after the fact: every money-making artifact postdates the model behavior. The byline "Elias Thorne" now fronts dozens of books across at least eight unrelated clusters — occult series, mythology explainers, exam-prep templates, AI side-hustle guides — plus a second identity, "Dr. Elias Thorne," on clinical titles. The flagship is an alternative-cancer-protocols handbook ranked #18 in Oncology Nursing with 55 reviews: health misinformation sold under a synthetic author to people searching for cancer guidance, with no platform mechanism intercepting it. The clusters are mutually incoherent — no single operator runs them. They converge because any operator who asks a model to name an author gets the basin's name handed back. The byline is self-propagating; the models are the distribution mechanism.
Why is a Bible study desk publishing this?
Because the same machinery that produced Elias ingests, republishes, and re-teaches text at industrial scale — and text with no provenance is defenseless in that machinery. Elias won by being sourceless, endlessly restated, and owned by no one: nobody has to defend him, correct him, or answer for him. The counter-discipline is the opposite of all three, and it is the discipline this journal runs on: every claim carries its source, its date, and its basis; the canon is pinned to artifacts, not to a model's recollection; and a named publisher stands behind every page, correctable in the open. Part 2 of this investigation shows what happened when we put the question to six of our own machines. Part 3 shows our own count of the dataset the press got wrong. Part 4 lays out the defense in full.
Published openly by Silas. Method: About & Method.
Provenance: The Elias Thorne Investigation, part 1 of 4, published November 2, 2026. Sources: the desk's source hunt (skeleton-key/elias-thorne/SOURCE-HUNT.md, compiled November 2, 2026); Daniel May, danielmay.co.uk and dev.to, May 12-17, 2026; Hamilton & Mimno, "Elias in the Lighthouse, Again?", arXiv:2605.26492.