Character-Name Concentration in LLM Fiction: Measuring Displacement and Mitigating Repetition

Alejandro Mozo Quesada, Sergio Gálvez Rojas, Francisco López ValverdearXiv 2026 · arXiv

TL;DR

LLM-generated fiction is notoriously repetitive, often over-relying on a handful of "AI slop" names like Elara and Elias. This paper introduces speculative naming, a fine-tuning-free, API-compatible method that reduces name repetition by 95% while maintaining the naturalness of character names.

What Problem Does This Paper Address?

If you’ve spent enough time reading AI-generated stories, you’ve likely met a lot of characters named Elara, Elias, or Leo. This phenomenon, dubbed "name slop," is a visible symptom of mode collapse—a narrowing of the model's creative output often caused by alignment processes like RLHF and DPO.

While researchers have developed ways to fix this at the "logit" level (the raw probability scores of the model), most users only have access to models via APIs. Simple fixes like "don't use these names" in a prompt often fail due to the balloon effect: if you ban Elara, the model simply picks a new favorite name and repeats it just as frequently. This paper seeks a way to control name concentration at the corpus level without needing access to model weights or retraining.

Methods

The authors propose Speculative Naming, which adapts the "draft-verify-reject" paradigm of speculative decoding to the level of character names. The process involves two passes:

  1. Scaffold: The model generates a story using placeholders like [CHAR_1].
  2. Draft: The model is asked to provide several candidate sets of names with "verbalized probabilities" (asking the model to state how likely it thinks a name is).
  3. Verify: Each name is scored using a SlopTracker. This tracker combines a "baseline fingerprint" (names the model is known to over-use) with a "runtime counter" (names used in the current generation run).
  4. Select: A selection rule (either a soft Boltzmann reweighting or a "HARD" threshold) chooses the best name set.
  5. Substitute: The placeholders in the original story are replaced with the chosen names.
Figure 1: The speculative naming pipeline. The model first writes a story with placeholders (scaffold), then drafts five name-sets with verbalized probabilities (draft). The SlopTracker, which combines a baseline fingerprint with a runtime counter, scores each candidate by its observed frequency (verify). Selection weights each candidate by the product of its stated probability and a freshness term (select), the placeholders are filled, and the tracker is updated (substitute). Blue stages are the speculative core; gray stages reuse the existing two-pass scaffold. The whole loop adds one extra model call over plain two-pass generation.

The core logic is captured in Algorithm 1, which inserts this speculative layer between the two passes of a standard story generation pipeline.

Algorithm 1: The Speculative Naming procedure.

To measure success, the authors introduce the Slop Ratio (SR), a list-free metric based on Simpson’s concentration index that calculates the probability of two characters in a corpus sharing the same name.

Datasets

The researchers conducted a massive empirical study to validate their method:

  • Corpus: 44,782 stories generated across 20 different LLMs (including Gemma, Qwen, GPT-4, and Llama families).
  • Languages: Stories were generated in English, Spanish, French, and German.
  • Stimuli: Models were prompted with either text-based or visual (pictogram) stimuli to ensure variety in story structure.
  • Validation: 88,919 named characters were extracted and matched against civil-registry name lists (like US Social Security data) to check for "naturalness."

Key Insights and Ideas

  • The Balloon Effect: Static banlists are ineffective. When the top 20 slop names are banned, models simply displace their concentration onto new "emergent" slop names. For example, banning Tiber in Gemma led to a surge in characters named Hemlock.
  • Language-Specific Slop: While some names like Leo are universal attractors, slop is largely language-specific. A banlist for English won't help a model writing in German.
  • Naturalness vs. Novelty: Banlists often force models to invent "fantasy-style" names that feel unnatural. Speculative naming, by contrast, keeps the name distribution close to human-authored baselines.
  • Vision Helps: Interestingly, providing a visual stimulus (images of pictograms) reduced name slop in most models compared to text-only prompts, likely because the visual grounding forced more specific creative choices.

Key Results

  • Massive Reduction: Speculative naming (HARD mode) reduced the Slop Ratio by 95% on average across all models.
  • Collision Probability: The mean probability of a name collision dropped from 7.3% to 0.4%.
  • Zero Known Slop: The method successfully held collisions with "known" slop names at zero.
  • Human Preference: In blinded evaluations, human readers preferred the names generated by speculative naming over baseline outputs, finding them more natural and creative.
  • Cost-Effectiveness: While it requires an extra model call, the method is budgetable and significantly more effective per token than multi-agent reviewer strategies.

Limitations and Future Work

The authors acknowledge several areas for further exploration:

  • Beyond Names: While the paper focuses on names, "slop" also exists in sensory clichés ("a shimmer of light") and formulaic openings ("In a world where..."). The authors provide a proof-of-concept for sentence openers but leave full mitigation to future work.
  • Cold Start: The runtime tracker needs a "warm-up" period (about 50 names) before it can effectively identify and penalize new emergent slop.
  • Discourse Level: The current method doesn't handle how characters are referred to throughout a story (e.g., alternating between full name, first name, and pronouns), which remains a challenge for LLM consistency.

Summary updated

Abstract

Character names in large language model (LLM) fiction concentrate on a handful of recurrent names such as 'Elara' and 'Elias', a measurable face of AI slop. Existing fixes either require logit access or retraining, or operate per request and cannot control concentration across a corpus. How much prompt-level strategies reduce concentration, and at what cost to name naturalness, has not been systematically measured. We present an empirical study of name-concentration control across eight strategies and introduce speculative naming, a fine-tuning-free method that adapts the draft-verify-reject paradigm of speculative decoding from tokens to names. The method requests candidate name-sets through verbalized sampling, scores them against a SlopTracker that combines a per-model fingerprint with a runtime counter, and selects through a temperature-controlled rule or its strict variant (HARD). We use 20 LLMs to generate 44,782 stories in four languages from text and visual stimuli (88,919 named characters), and measure concentration with a list-free collision metric (Slop Ratio, SR) decomposed into known and emergent components. List-based strategies do not remove slop: static banlists displace concentration to emergent names and more than halve the share of attested real names. Speculative naming removes it: the sampling scaffold alone cuts SR by 89% on average, the dynamic tracker brings the total reduction to 95%, mean collision probability falls from 7.3% to 0.4%, and known-name collisions hold at zero while naturalness stays close to baseline (42-69% attested by language) and within-story collisions drop from 4.3% to 0.2%. The strategy ranking is stable across languages, model families, and name-counting conventions. Name concentration is thus controllable at the corpus level without logit access or retraining; broader creative diversity beyond naming remains open.
BibTeX
@misc{quesada2026character,
  author = {Alejandro Mozo Quesada and Sergio Gálvez Rojas and Francisco López Valverde},
  title = {{Character-Name Concentration in LLM Fiction: Measuring Displacement and Mitigating Repetition}},
  year = {2026},
  eprint = {2611.01284},
  archivePrefix = {arXiv},
  url = {https://arxiv.org/abs/2611.01284},
}
Figure