Triple

T15423491
Position Surface form Disambiguated ID Type / Status
Subject Wakenda, Missouri E369444 entity
Predicate hasName P744 FINISHED
Object Wakenda, Missouri E1080280 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: Wakenda, Missouri | Statement: [Wakenda, Missouri, hasName, Wakenda, Missouri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wakenda, Missouri
Context triple: [Wakenda, Missouri, hasName, Wakenda, Missouri]
  • A. Wakenda, Missouri
    Wakenda, Missouri is a small unincorporated rural community located in Clinton County in the U.S. state of Missouri.
  • B. Wakenda, Missouri chosen
    Wakenda, Missouri is a small unincorporated community located in Carroll County in the north-central region of the state.
  • C. Waverly, Missouri
    Waverly, Missouri is a small town in central Missouri along the Missouri River, historically known as an agricultural community.
  • D. Wilcox, Missouri
    Wilcox, Missouri is a small unincorporated rural community located in Nodaway County in the northwestern part of the state.
  • E. Auxvasse, Missouri
    Auxvasse, Missouri is a small city in central Missouri known for its rural character and location within Callaway County.
  • 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_69d85a1849f48190bf898068b2806fae completed April 10, 2026, 2:02 a.m.
NER Named-entity recognition batch_69e03ec032548190840b558dde6057c7 completed April 16, 2026, 1:43 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff1a7d02a08190a1e34e3a014acea9 completed May 9, 2026, 11:29 a.m.
Created at: April 10, 2026, 3:20 a.m.