Triple

T14573933
Position Surface form Disambiguated ID Type / Status
Subject Berkeley, Missouri E341988 entity
Predicate locatedNear P294 FINISHED
Object Edmundson, Missouri E823250 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: Edmundson, Missouri | Statement: [Berkeley, Missouri, locatedNear, Edmundson, Missouri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Edmundson, Missouri
Context triple: [Berkeley, Missouri, locatedNear, Edmundson, Missouri]
  • A. Edmundson, Missouri chosen
    Edmundson, Missouri is a small suburban city in St. Louis County that forms part of the greater St. Louis metropolitan area.
  • B. Easton, Missouri
    Easton, Missouri is a small rural village in northwestern Missouri that forms part of the St. Joseph metropolitan area.
  • C. Auxvasse, Missouri
    Auxvasse, Missouri is a small city in central Missouri known for its rural character and location within Callaway County.
  • D. Steedman, Missouri
    Steedman, Missouri is a small unincorporated rural community located in Callaway County in the U.S. state of Missouri.
  • E. Bellamy, Missouri
    Bellamy, Missouri is a small unincorporated community located in rural Vernon County in the western part of the state.
  • 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_69d822dcc6248190bed689984bceb0e2 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb3f49d58819094fcd2a702e146cb completed April 14, 2026, 9:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69fe64ea085c8190b308504fa11c731d completed May 8, 2026, 10:34 p.m.
Created at: April 10, 2026, 1:24 a.m.