Triple

T8870194
Position Surface form Disambiguated ID Type / Status
Subject Callaway County E211133 entity
Predicate containsSettlement P847 FINISHED
Object Auxvasse, Missouri E598363 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: Auxvasse, Missouri | Statement: [Callaway County, containsSettlement, Auxvasse, Missouri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Auxvasse, Missouri
Context triple: [Callaway County, containsSettlement, Auxvasse, Missouri]
  • A. Auxvasse, Missouri chosen
    Auxvasse, Missouri is a small city in central Missouri known for its rural character and location within Callaway County.
  • B. Levasy, Missouri
    Levasy, Missouri is a small rural city located in eastern Jackson County within the Kansas City metropolitan area.
  • C. Elkhorn, Missouri
    Elkhorn, Missouri is a small unincorporated rural community located in Ray County in the U.S. state of Missouri.
  • D. Wilcox, Missouri
    Wilcox, Missouri is a small unincorporated rural community located in Nodaway County in the northwestern part of the state.
  • E. Yates, Missouri
    Yates, Missouri is a small unincorporated community located in Randolph 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_69ca838d3c7c8190a849566d5afd2b11 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc6126d2f88190979ab25772ee657c completed April 1, 2026, 12:04 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfba113870819096438aebeddbf34a completed April 3, 2026, 1:01 p.m.
Created at: March 30, 2026, 6:51 p.m.