Triple
T33708677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 220 in North Carolina |
E863673
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | segment of U.S. Route 220 |
C58930
|
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: segment of U.S. Route 220 Context triple: [U.S. Route 220 in North Carolina, instanceOf, segment of U.S. Route 220]
-
A.
auxiliary route of U.S. Route 20
An auxiliary route of U.S. Route 20 is a supplementary highway, such as a business, bypass, or spur route, that branches from and reconnects to the main U.S. Route 20 to serve specific local or regional traffic needs.
-
B.
branch of the Pennsylvania Turnpike
A branch of the Pennsylvania Turnpike is a secondary toll highway segment that diverges from the main Turnpike to provide additional regional connectivity and access to surrounding areas.
-
C.
segment of Washington State Route 99
A segment of Washington State Route 99 represents a continuous portion of the state highway between two defined endpoints, characterized by its specific location, roadway features, and role in regional transportation.
-
D.
Nevada State Route
A Nevada State Route is a numbered highway within the state of Nevada that is part of the state-maintained road network, facilitating regional and local transportation.
-
E.
U.S. Highway business route
A U.S. Highway business route is a special alignment of a U.S. Highway that diverts from the main route to pass through the downtown or commercial center of a city or town, providing local access to businesses and services.
- F. None of above. chosen
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_69f3498844608190bb8f9b14908d2510 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:43 a.m.