Triple
T10748128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kentucky Route 1958 |
E253503
|
entity |
| Predicate | routeDesignation |
P1864
|
FINISHED |
| Object |
KY 1958
KY 1958 is a state highway in Kentucky that serves as a designated route within the Kentucky state highway system.
|
E884347
|
NE FINISHED |
How this triple was built (4 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 1958 | Statement: [Kentucky Route 1958, routeDesignation, KY 1958]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KY 1958 Context triple: [Kentucky Route 1958, routeDesignation, KY 1958]
-
A.
KY 80
KY 80 is a major east–west state highway running across much of Kentucky, connecting numerous towns and cities along its route.
-
B.
KY 84
KY 84 is a state highway in Kentucky that serves as a regional connector route through several central Kentucky counties.
-
C.
KY 1500
KY 1500 is a state highway in Kentucky that serves as a minor regional connector within the state's road network.
-
D.
KY 210
KY 210 is a state highway in Kentucky that connects the city of Elizabethtown with the Campbellsville area, serving as a regional route through central Kentucky.
-
E.
KY 313
KY 313 is a state highway in Kentucky that serves as a regional connector route, primarily in the central part of the state.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: KY 1958 Triple: [Kentucky Route 1958, routeDesignation, KY 1958]
Generated description
KY 1958 is a state highway in Kentucky that serves as a designated route within the Kentucky state highway system.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: KY 1958 Target entity description: KY 1958 is a state highway in Kentucky that serves as a designated route within the Kentucky state highway system.
-
A.
KY 80
KY 80 is a major east–west state highway running across much of Kentucky, connecting numerous towns and cities along its route.
-
B.
KY 84
KY 84 is a state highway in Kentucky that serves as a regional connector route through several central Kentucky counties.
-
C.
KY 1500
KY 1500 is a state highway in Kentucky that serves as a minor regional connector within the state's road network.
-
D.
KY 210
KY 210 is a state highway in Kentucky that connects the city of Elizabethtown with the Campbellsville area, serving as a regional route through central Kentucky.
-
E.
KY 313
KY 313 is a state highway in Kentucky that serves as a regional connector route, primarily in the central part of the state.
- F. None of above. chosen
Provenance (5 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d711b9242c81908dbf3fa155159b3c |
completed | April 9, 2026, 2:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69de231af7388190b73347a3ffc1077a |
completed | April 14, 2026, 11:20 a.m. |
| NEDg | Description generation | batch_69de27fb843c81908c0d0a5fb231543f |
completed | April 14, 2026, 11:41 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69de2dff4a048190823c8b5f1f7ea548 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 8, 2026, 9:15 p.m.