Triple
T11716508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kentucky Route 728 |
E278511
|
entity |
| Predicate | hasJunctionWith |
P1018
|
FINISHED |
| Object | Kentucky Route 1827 |
E943378
|
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 Route 1827 | Statement: [Kentucky Route 728, hasJunctionWith, Kentucky Route 1827]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kentucky Route 1827 Context triple: [Kentucky Route 728, hasJunctionWith, Kentucky Route 1827]
-
A.
Kentucky Route 1827
chosen
Kentucky Route 1827 is a state highway in Kentucky that serves as a local connector route within the state’s secondary road network.
-
B.
Kentucky Route 181
Kentucky Route 181 is a state highway in Kentucky that connects the city of Elkton with other communities in the region.
-
C.
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.
-
D.
Kentucky Route 1681
Kentucky Route 1681 is a state highway in Kentucky that serves as a local connector route within the Lexington area.
-
E.
Kentucky Route 152
Kentucky Route 152 is a state highway in Kentucky that connects several central Kentucky communities, including Harrodsburg, and provides regional east–west travel.
- 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_69d6aaff2ce88190b4a1e4b341ad5377 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4c10d988190842acd824135cf15 |
completed | April 10, 2026, 7:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f08fed49fc8190951ff3af6bd51050 |
completed | April 28, 2026, 10:46 a.m. |
Created at: April 8, 2026, 9:40 p.m.