Triple

T19760297
Position Surface form Disambiguated ID Type / Status
Subject Arkoe, Missouri E474609 entity
Predicate hasOfficialName P66 FINISHED
Object Arkoe, 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: Arkoe, Missouri | Statement: [Arkoe, Missouri, hasOfficialName, Arkoe, Missouri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Arkoe, Missouri
Context triple: [Arkoe, Missouri, hasOfficialName, Arkoe, Missouri]
  • A. Arkoe, Missouri chosen
    Arkoe, Missouri is a small rural village located in Nodaway County in the northwestern part of the state.
  • B. Argyle, Missouri
    Argyle, Missouri is a small village in Maries and Osage counties known for its rural character within central Missouri.
  • C. Ozark, Missouri
    Ozark, Missouri is a small city in Christian County known as part of the Springfield metropolitan area and for its proximity to the Ozark Mountains and outdoor recreation.
  • D. Auxvasse, Missouri
    Auxvasse, Missouri is a small city in central Missouri known for its rural character and location within Callaway County.
  • 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 (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_69d8e51940a0819087bd2996f98da668 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e6531f38b48190b1663870a8da5a59 completed April 20, 2026, 4:23 p.m.
Created at: April 10, 2026, 1:48 p.m.