Triple

T15761049
Position Surface form Disambiguated ID Type / Status
Subject Missouri Route 24 E382096 entity
Predicate connects P390 FINISHED
Object Keytesville, Missouri E567112 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: Keytesville, Missouri | Statement: [Missouri Route 24, connects, Keytesville, Missouri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Keytesville, Missouri
Context triple: [Missouri Route 24, connects, Keytesville, Missouri]
  • A. Keytesville, Missouri chosen
    Keytesville, Missouri is a small rural city that serves as the county seat of Chariton County in northeastern Missouri.
  • B. Auxvasse, Missouri
    Auxvasse, Missouri is a small city in central Missouri known for its rural character and location within Callaway County.
  • C. Kingsville, Missouri
    Kingsville, Missouri is a small rural village located in Johnson County in the western part of the state.
  • D. Rockville, Missouri
    Rockville, Missouri is a small rural town located in Bates County in western Missouri, known for its agricultural surroundings and close-knit community.
  • 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_69d86d9e6b44819085d1f6a969ecb74c completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e050b52c548190a0ffa4493a4eb15c completed April 16, 2026, 3 a.m.
NED1 Entity disambiguation (via context triple) batch_69ffe4670e8881908bc9f3879ba208ba completed May 10, 2026, 1:50 a.m.
Created at: April 10, 2026, 4:47 a.m.