Lost in Stories: Consistency Bugs in Long Story Generation by LLMs (ConStory-Bench / ConStory-Checker)
Source: https://arxiv.org/abs/2603.05890
Project page https://picrew.github.io/constory-bench.github.io/ lists the five categories: Timeline & Plot Logic, Characterization, World-building & Setting, Factual & Detail Consistency, Narrative & Style. Leaderboard not read.
Structured fields
{
"archived": false,
"revision": {
"ref": "v1 (submitted 6 Mar 2026; only version listed)",
"pinned": true,
"source_url": "https://arxiv.org/abs/2603.05890"
},
"checked_at": "2026-10-17T00:00:00.000Z",
"usefulness": "Benchmark and LLM-as-judge pipeline for contradictions in long generated stories (2,000 prompts, five error categories, 19 subtypes), with MIT-licensed code and dataset. The only surveyed source that publishes a runnable consistency checker; it judges generated stories, not hand-written series canon.",
"source_type": "paper",
"availability": "available",
"dependencies": [
"Python",
"OpenAI-compatible LLM API"
],
"source_owner": "Junjie Li, Xinrui Guo, Yuhao Wu, Roy Ka-Wei Lee, Hongzhi Li, Yutao Xie",
"next_check_at": "2026-10-31T00:00:00.000Z",
"hardware_notes": "No local hardware requirement stated; README says story generation can use any OpenAI-compatible API, including local servers (vLLM, Ollama); judge-model requirements are not stated.",
"known_limitations": [
"Judges LLM-generated stories (English and Chinese); no series-canon or human-written-script evaluation is reported.",
"CED and GRR metrics are named in the README but not defined in what was read.",
"The checker is an LLM-as-judge; which judge models it supports and what it costs are not stated in the README read (the README says story generation can use any OpenAI-compatible API, including local servers)."
],
"upstream_updated_at": "2026-03-06T04:16:46.000Z"
}Evidence claims
- [upstream_claim] Abstract: ConStory-Bench evaluates narrative consistency in long-form story generation. · locator: Abstract source
- [upstream_claim] Abstract: 2,000 prompts across four task scenarios and a taxonomy of five error categories with 19 fine-grained subtypes. · locator: Abstract source
- [upstream_claim] Abstract: ConStory-Checker detects contradictions and grounds each judgment in explicit textual evidence. · locator: Abstract source
- [upstream_claim] Abstract: consistency errors are most common in factual and temporal dimensions. · locator: Abstract source
- [sourced_fact] GitHub README: the checker is an LLM-as-judge (judge.py) with 5 categories and 19 subtypes. · locator: README source
- [sourced_fact] GitHub README: story generation can use any OpenAI-compatible API. · locator: README, 'How to run' source
- [sourced_fact] HF API: dataset license MIT. · locator: HF API cardData source
- [sourced_fact] HF card: id column documents prompt IDs 0-1999. · locator: HF dataset card schema source
- [sourced_fact] GitHub API: code repository Picrew/ConStory-Bench is MIT-licensed and not archived. · locator: evidence/github/picrew--constory-bench.json source
- [upstream_claim] Research review verdict at export: reviewed (as of 2026-10-17). Recorded by the research pipeline, not a hub review outcome; evidence.review stays unreviewed until an independent reviewer records one.
Rights
| component | license | hosting | redistribution | modification | training | Evidence and notes |
|---|---|---|---|---|---|---|
| code | MIT | permitted | permitted | permitted | unknown | MIT per GitHub API (repo pushed 2026-04-07); README says MIT. No training rights implied. |
| dataset | MIT | permitted | permitted | permitted | unknown | HF card/API: MIT. The data include generated stories (schema field generated_story) from many LLMs; those providers' output terms are not addressed by the dataset license. |
| documentation | unknown | unknown | unknown | unknown | unknown | arXiv abs page links the arXiv non-exclusive distribution license 1.0 for the paper text; that license grants arXiv distribution rights and its third-party reuse terms were not read. |
Linked records
- Do LLM plot-hole and consistency detectors work on multi-episode series canon, not just short stories or generated text? discusses → this
- Steps, each attributed. (1) Keep canon in a structured store the agent can read: Kanka exposes characters, locations, items and custom categories as entities with posts, properties, tags and connections through a REST API v1.0 (personal access token, acts on live data, no dry-run mode); bibisco kee… cites → this
- MovieSum: the dataset card body states Creative Commons Attribution Non Commercial 4.0, but the HF API record has no license tag and the card does not say where the 2,200 screenplays came from. FlawedFictions (kahuja/flawed-fictions): HF tags license MIT, but the card README is empty, so source-sto… cites → this
- FlawedFictions tests whether an LLM spots a plot hole in a short human-written story, using an algorithm that injects plot holes (reported: state-of-the-art LLMs struggle regardless of reasoning effort and degrade as stories get longer; LLM summaries and generated stories introduce plot holes). Con… cites → this