Triple

T11210978
Position Surface form Disambiguated ID Type / Status
Subject Kentucky Route 676 E265305 entity
Predicate abbreviation P43 FINISHED
Object KY 676 E265305 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: KY 676 | Statement: [Kentucky Route 676, abbreviation, KY 676]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: KY 676
Context triple: [Kentucky Route 676, abbreviation, KY 676]
  • A. Kentucky Route 676 chosen
    Kentucky Route 676 is a state highway in Kentucky that serves as a key east–west connector through Franklin County, including the city of Frankfort.
  • B. D605 highway
    The D605 highway is a major Turkish road that runs through Kocaeli Province, connecting local towns and facilitating regional transportation.
  • C. B676 road
    The B676 road is a minor British roadway in England that connects several rural communities and links with major routes such as the A1 near Colsterworth.
  • D. Kentucky Route 1638
    Kentucky Route 1638 is a state highway in Kentucky that serves as a local connector route in and around the city of Muldraugh.
  • E. B6318 road
    The B6318 road is a major route in northern England that closely follows the line of Hadrian's Wall, connecting various towns and historical sites along its course.
  • 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_69d6aac59460819089b9848b27f57848 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e8d6f5d4819086dcb776a0d469e8 completed April 9, 2026, 5:58 p.m.
NED1 Entity disambiguation (via context triple) batch_69e49747ec288190bc3e826b6de7f6f2 completed April 19, 2026, 8:50 a.m.
Created at: April 8, 2026, 9:30 p.m.