Triple

T20768482
Position Surface form Disambiguated ID Type / Status
Subject U.S. Route 31E E511162 entity
Predicate overlapsWith P1867 FINISHED
Object Kentucky Route 80 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: Kentucky Route 80 | Statement: [U.S. Route 31E, overlapsWith, Kentucky Route 80]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kentucky Route 80
Context triple: [U.S. Route 31E, overlapsWith, Kentucky Route 80]
  • A. Kentucky Route 80 chosen
    Kentucky Route 80 is a major east–west highway spanning much of Kentucky, connecting numerous towns and cities across the southern part of the state.
  • B. Kentucky Route 88
    Kentucky Route 88 is a state highway in Kentucky that serves as an important east–west connector through rural communities, including parts of Hart County.
  • C. Kentucky Route 90
    Kentucky Route 90 is a significant east–west state highway in south-central Kentucky that connects several communities and serves as a key regional transportation corridor.
  • D. Kentucky Route 70
    Kentucky Route 70 is an east–west state highway in Kentucky that spans much of the state, connecting numerous small towns and rural areas.
  • E. Kentucky Route 84
    Kentucky Route 84 is a state highway in Kentucky that runs through central parts of the state, connecting communities such as Hodgenville and serving as a regional connector route.
  • 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_69e0b4ca01148190ac018e57e0cab46f completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c24fa1b08190b09ab8fcb87b5c01 completed April 21, 2026, 12:18 a.m.
Created at: April 16, 2026, 12:36 p.m.