Triple
T22275607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Highways in Tennessee |
E550593
|
entity |
| Predicate | hasRoute |
P4374
|
FINISHED |
| Object | U.S. Route 321 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 321 in Tennessee | Statement: [U.S. Highways in Tennessee, hasRoute, U.S. Route 321 in Tennessee]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: U.S. Route 321 in Tennessee Context triple: [U.S. Highways in Tennessee, hasRoute, U.S. Route 321 in Tennessee]
-
A.
U.S. Route 231 in Tennessee
U.S. Route 231 in Tennessee is a north–south federal highway that connects several central Tennessee communities as part of the broader U.S. Route 231 corridor.
-
B.
U.S. Route 31 in Tennessee
U.S. Route 31 in Tennessee is a major north–south U.S. Highway corridor that passes through central Tennessee, connecting communities between the Alabama border and the Nashville metropolitan area.
-
C.
U.S. Route 72 in Tennessee
U.S. Route 72 in Tennessee is a major east–west U.S. Highway that connects the Mississippi state line to Chattanooga, serving as an important regional corridor in the southern part of the state.
-
D.
U.S. Route 31W in Tennessee
U.S. Route 31W in Tennessee is a north–south U.S. Highway that runs through central Tennessee, connecting Nashville with the Kentucky state line and serving as a key regional corridor.
-
E.
U.S. Route 11E in Tennessee
U.S. Route 11E in Tennessee is a major northeast–southwest highway that connects several cities in eastern Tennessee, including Knoxville and Johnson City, serving as an important regional transportation corridor.
- 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 321 in Tennessee Target entity description: U.S. Route 321 in Tennessee is a north–south U.S. highway that connects the Great Smoky Mountains region with cities such as Gatlinburg, Pigeon Forge, and Knoxville, serving as a key corridor for tourism and regional travel.
-
A.
U.S. Route 231 in Tennessee
U.S. Route 231 in Tennessee is a north–south federal highway that connects several central Tennessee communities as part of the broader U.S. Route 231 corridor.
-
B.
U.S. Route 31 in Tennessee
U.S. Route 31 in Tennessee is a major north–south U.S. Highway corridor that passes through central Tennessee, connecting communities between the Alabama border and the Nashville metropolitan area.
-
C.
U.S. Route 72 in Tennessee
U.S. Route 72 in Tennessee is a major east–west U.S. Highway that connects the Mississippi state line to Chattanooga, serving as an important regional corridor in the southern part of the state.
-
D.
U.S. Route 31W in Tennessee
U.S. Route 31W in Tennessee is a north–south U.S. Highway that runs through central Tennessee, connecting Nashville with the Kentucky state line and serving as a key regional corridor.
-
E.
U.S. Route 11E in Tennessee
U.S. Route 11E in Tennessee is a major northeast–southwest highway that connects several cities in eastern Tennessee, including Knoxville and Johnson City, serving as an important regional transportation corridor.
- 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.