Triple
T22275585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Highways in Tennessee |
E550593
|
entity |
| Predicate | hasRoute |
P4374
|
FINISHED |
| Object | U.S. Route 25E in Tennessee |
—
|
NE NERFINISHED |
How this triple was built (3 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: U.S. Route 25E in Tennessee | Statement: [U.S. Highways in Tennessee, hasRoute, U.S. Route 25E in Tennessee]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: U.S. Route 25E in Tennessee Context triple: [U.S. Highways in Tennessee, hasRoute, U.S. Route 25E in Tennessee]
-
A.
Tennessee State Route 25
Tennessee State Route 25 is a state highway in northern Middle Tennessee that runs east–west through communities such as Carthage, connecting local towns and facilitating regional travel.
-
B.
U.S. Route 25 in North Carolina
U.S. Route 25 in North Carolina is a north–south United States highway that runs through the western part of the state, connecting the Asheville area to the South Carolina border and serving as a key regional transportation corridor.
-
C.
Tennessee State Route 59
Tennessee State Route 59 is a state highway in western Tennessee that serves as an important east–west connector through rural communities, including the area near Covington.
-
D.
Tennessee State Route 55
Tennessee State Route 55 is a state highway in Middle Tennessee that connects several communities, including McMinnville, and serves as an important regional route for local and through traffic.
-
E.
Tennessee State Route 56
Tennessee State Route 56 is a north–south state highway in Tennessee that connects multiple towns and rural areas across the state’s central region.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: U.S. Route 25E in Tennessee Target entity description: U.S. Route 25E in Tennessee is a major north–south highway in the eastern part of the state that serves as a key corridor through the Appalachian region, connecting communities and facilitating regional travel and commerce.
-
A.
Tennessee State Route 25
Tennessee State Route 25 is a state highway in northern Middle Tennessee that runs east–west through communities such as Carthage, connecting local towns and facilitating regional travel.
-
B.
U.S. Route 25 in North Carolina
U.S. Route 25 in North Carolina is a north–south United States highway that runs through the western part of the state, connecting the Asheville area to the South Carolina border and serving as a key regional transportation corridor.
-
C.
Tennessee State Route 59
Tennessee State Route 59 is a state highway in western Tennessee that serves as an important east–west connector through rural communities, including the area near Covington.
-
D.
Tennessee State Route 55
Tennessee State Route 55 is a state highway in Middle Tennessee that connects several communities, including McMinnville, and serves as an important regional route for local and through traffic.
-
E.
Tennessee State Route 56
Tennessee State Route 56 is a north–south state highway in Tennessee that connects multiple towns and rural areas across the state’s central region.
- F. None of above. chosen
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_69e11e43d8208190aff4f9cf7f2c2a8a |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f14ea7ebbc8190948e8994e988adb3 |
completed | April 29, 2026, 12:19 a.m. |
Created at: April 16, 2026, 8:40 p.m.