Triple

T16813198
Position Surface form Disambiguated ID Type / Status
Subject Linn County, Missouri E408667 entity
Predicate hasCity P316 FINISHED
Object Linneus, Missouri E1235198 NE FINISHED

How this triple was built (2 steps)

Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Linneus, Missouri | Statement: [Linn County, Missouri, hasCity, Linneus, Missouri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Linneus, Missouri
Context triple: [Linn County, Missouri, hasCity, Linneus, Missouri]
  • A. Linneus, Missouri chosen
    Linneus, Missouri is a small Midwestern city that serves as the administrative and governmental center of Linn County in northern Missouri.
  • B. Linn, Missouri
    Linn, Missouri is a small city in Osage County that serves as the county seat and is part of the Jefferson City metropolitan region.
  • C. Nelson, Missouri
    Nelson, Missouri is a small city located in central Missouri within Saline County, known for its rural community character.
  • D. Rinehart, Missouri
    Rinehart, Missouri is a small unincorporated community located in Vernon County in the western part of the U.S. state of Missouri.
  • E. Elkhorn, Missouri
    Elkhorn, Missouri is a small unincorporated rural community located in Ray County in the U.S. state of Missouri.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 batches)

The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.

Step Stage Batch ID Status When
creating Elicitation batch_69d88394566c8190b3dcbdc72935f7fa completed April 10, 2026, 4:59 a.m.
NER Named-entity recognition batch_69e3b2df5c888190a462614e1432c357 completed April 18, 2026, 4:35 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00c79cdf9c8190aa20d536ca17ab81 completed May 10, 2026, 5:59 p.m.
Created at: April 10, 2026, 5:23 a.m.