Triple

T20558237
Position Surface form Disambiguated ID Type / Status
Subject U.S. Highways in Missouri E504776 entity
Predicate hasRoute P4374 FINISHED
Object U.S. Route 50 in Missouri NE NERFINISHED

How this triple was built (3 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: U.S. Route 50 in Missouri | Statement: [U.S. Highways in Missouri, hasRoute, U.S. Route 50 in Missouri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: U.S. Route 50 in Missouri
Context triple: [U.S. Highways in Missouri, hasRoute, U.S. Route 50 in Missouri]
  • A. U.S. Route 40 in Missouri
    U.S. Route 40 in Missouri is a major east–west federal highway segment that traverses the state, connecting key cities and serving as part of a historic transcontinental route.
  • B. U.S. Route 50 in Jefferson City, Missouri
    U.S. Route 50 in Jefferson City, Missouri is a major east–west U.S. highway segment that serves the state capital area, connecting with several key routes and facilitating regional and cross-state travel.
  • C. U.S. Route 59 in Missouri
    U.S. Route 59 in Missouri is a north–south U.S. Highway that runs through the western part of the state, connecting rural communities and regional centers as part of a larger multistate route from Texas to Minnesota.
  • D. U.S. Route 50 in Ohio
    U.S. Route 50 in Ohio is a major east–west U.S. Highway that traverses the southern part of the state, linking cities such as Cincinnati and Athens as part of its cross-country route.
  • E. U.S. Route 60 (Missouri)
    U.S. Route 60 (Missouri) is a major east–west U.S. Highway crossing southern Missouri, connecting numerous towns and cities as part of the national U.S. Route 60 corridor.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: U.S. Route 50 in Missouri
Target entity description: U.S. Route 50 in Missouri is a major east–west highway that traverses the state, connecting rural communities with key urban centers such as Kansas City and Jefferson City.
  • A. U.S. Route 40 in Missouri
    U.S. Route 40 in Missouri is a major east–west federal highway segment that traverses the state, connecting key cities and serving as part of a historic transcontinental route.
  • B. U.S. Route 50 in Jefferson City, Missouri chosen
    U.S. Route 50 in Jefferson City, Missouri is a major east–west U.S. highway segment that serves the state capital area, connecting with several key routes and facilitating regional and cross-state travel.
  • C. U.S. Route 59 in Missouri
    U.S. Route 59 in Missouri is a north–south U.S. Highway that runs through the western part of the state, connecting rural communities and regional centers as part of a larger multistate route from Texas to Minnesota.
  • D. U.S. Route 50 in Ohio
    U.S. Route 50 in Ohio is a major east–west U.S. Highway that traverses the southern part of the state, linking cities such as Cincinnati and Athens as part of its cross-country route.
  • E. U.S. Route 60 (Missouri)
    U.S. Route 60 (Missouri) is a major east–west U.S. Highway crossing southern Missouri, connecting numerous towns and cities as part of the national U.S. Route 60 corridor.
  • F. None of above.

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_69e0b4b6587c8190aee63dc7cff244ea completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6a5df84088190848c7eb35564d8f9 completed April 20, 2026, 10:17 p.m.
Created at: April 16, 2026, 11:38 a.m.