Triple

T20791509
Position Surface form Disambiguated ID Type / Status
Subject Missouri River corridor E511788 entity
Predicate connects P390 FINISHED
Object Waverly, 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: Waverly, Missouri | Statement: [Missouri River corridor, connects, Waverly, Missouri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Waverly, Missouri
Context triple: [Missouri River corridor, connects, Waverly, Missouri]
  • A. Waverly, Missouri chosen
    Waverly, Missouri is a small town in central Missouri along the Missouri River, historically known as an agricultural community.
  • B. Weatherby, Missouri
    Weatherby, Missouri is a small rural village located in DeKalb County in the northwestern part of the U.S. state of Missouri.
  • C. Willard, Missouri
    Willard, Missouri is a small suburban city in southwestern Missouri, located near Springfield and known for its family-friendly community and access to regional amenities.
  • D. Wilcox, Missouri
    Wilcox, Missouri is a small unincorporated rural community located in Nodaway County in the northwestern part of the state.
  • E. Estill, Missouri
    Estill, Missouri is a small unincorporated community located in Howard County in the central part of the state.
  • 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_69e0b4cb83948190bd57bec21d78ed53 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c2910d488190bc4be37512effc86 completed April 21, 2026, 12:19 a.m.
Created at: April 16, 2026, 12:38 p.m.