Triple

T18438522
Position Surface form Disambiguated ID Type / Status
Subject U.S. Route 64 E450459 entity
Predicate runsThrough P416 FINISHED
Object Guymon, Oklahoma 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: Guymon, Oklahoma | Statement: [U.S. Route 64, runsThrough, Guymon, Oklahoma]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Guymon, Oklahoma
Context triple: [U.S. Route 64, runsThrough, Guymon, Oklahoma]
  • A. Guymon chosen
    Guymon is a small city in the Oklahoma Panhandle known as an agricultural and energy-production hub for the surrounding High Plains region.
  • B. Comanche, Oklahoma
    Comanche, Oklahoma is a small city in southern Oklahoma known for its agricultural roots and close-knit rural community.
  • C. Concho, Oklahoma
    Concho, Oklahoma is an unincorporated community in Canadian County best known as the headquarters of the Cheyenne and Arapaho Tribes.
  • D. Parkland, Oklahoma
    Parkland, Oklahoma is a small unincorporated rural community located in Lincoln County in the central part of the state.
  • E. Muskogee, Oklahoma
    Muskogee, Oklahoma is a city in eastern Oklahoma known historically as a regional commercial and transportation hub and for its role in Native American and frontier history.
  • 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_69d8d381d6388190a9e94e9c658174e4 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e51c0ed6708190ae90efd8455ec352 completed April 19, 2026, 6:16 p.m.
Created at: April 10, 2026, 11:29 a.m.