Triple
T25268988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tennessee State Route 330 |
E633512
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | road in Tennessee |
C16272
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: road in Tennessee Context triple: [Tennessee State Route 330, instanceOf, road in Tennessee]
-
A.
numbered highway in Tennessee
chosen
A numbered highway in Tennessee is a designated state or U.S. route within Tennessee’s road network, identified by a unique number and maintained for regional and interstate transportation.
-
B.
road in Kentucky
A road in Kentucky is a designated transportation route within the state’s boundaries that facilitates vehicular travel between localities, landmarks, and regions, following Kentucky’s specific geographic, legal, and infrastructural standards.
-
C.
road in West Virginia
A road in West Virginia is a transportation route, ranging from winding rural byways to major highways, that traverses the state's mountainous terrain to connect its towns, cities, and natural landmarks.
-
D.
road in Great Smoky Mountains National Park
A road in Great Smoky Mountains National Park is a paved or unpaved transportation corridor winding through the park’s mountainous terrain, providing vehicular access to natural features, scenic overlooks, and visitor facilities while being managed to minimize environmental impact.
-
E.
road in Virginia
A road in Virginia is a designated vehicular travelway within the Commonwealth of Virginia that facilitates transportation, access, and connectivity between locations while adhering to state and local regulations and infrastructure standards.
- F. None of above.
Provenance (1 batch)
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_69e75a92f48881909974ff9c11150a2e |
completed | April 21, 2026, 11:08 a.m. |
Created at: April 21, 2026, 1:16 p.m.