Triple

T5851338
Position Surface form Disambiguated ID Type / Status
Subject U.S. Route 68 E130037 entity
Predicate runsThrough P416 FINISHED
Object Kentucky E18292 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: Kentucky | Statement: [U.S. Route 68, runsThrough, Kentucky]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kentucky
Context triple: [U.S. Route 68, runsThrough, Kentucky]
  • A. Kentucky chosen
    Kentucky is a southeastern U.S. state known for its horse racing, bourbon distilleries, bluegrass music, and diverse landscapes ranging from Appalachian mountains to fertile river valleys.
  • B. Kentucky and Missouri
    Kentucky and Missouri are neighboring U.S. states in the central United States whose shared boundary is largely defined by the Mississippi River.
  • C. Indiana and Kentucky
    Indiana and Kentucky are neighboring U.S. states in the Midwest and Upper South, respectively, separated in large part by the Ohio River.
  • D. Kentucky and Illinois
    Kentucky and Illinois are neighboring U.S. states in the Midwest and Upper South that meet along the Mississippi River.
  • E. Vantucky
    Vantucky is a colloquial, often tongue-in-cheek nickname for Vancouver, Washington, referencing its perceived rural or small-town character.
  • 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_69c0084de39081909eb34e6bed74215a completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c035176c8c81909e24d263e4feb664 completed March 22, 2026, 6:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0b0e20c208190b861fa8066852efc completed March 23, 2026, 3:17 a.m.
Created at: March 22, 2026, 3:55 p.m.