Triple

T23429276
Position Surface form Disambiguated ID Type / Status
Subject Elston, Missouri E563279 entity
Predicate hasName P744 FINISHED
Object Elston, Missouri NE NERFINISHED

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: Elston, Missouri | Statement: [Elston, Missouri, hasName, Elston, Missouri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Elston, Missouri
Context triple: [Elston, Missouri, hasName, Elston, Missouri]
  • A. Elston, Missouri chosen
    Elston, Missouri is a small unincorporated community located in Cole County in the central part of the state.
  • B. Estill, Missouri
    Estill, Missouri is a small unincorporated community located in Howard County in the central part of the state.
  • C. Easton, Missouri
    Easton, Missouri is a small rural village in northwestern Missouri that forms part of the St. Joseph metropolitan area.
  • D. Ellis, Missouri
    Ellis, Missouri is a small unincorporated community located in Vernon County in the western part of the U.S. state of Missouri.
  • E. Foristell, Missouri
    Foristell, Missouri is a small city in eastern Missouri that spans St. Charles and Warren counties and serves as a rural-residential community along Interstate 70.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e24553980c8190bb66a2ae0bdab125 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f1a54ba29881909945690496f28d65 completed April 29, 2026, 6:29 a.m.
Created at: April 17, 2026, 5:48 p.m.