Triple
T33630109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 23 in North Carolina |
E861527
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | segment of U.S. Route 23 |
C1129
|
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 23 Context triple: [U.S. Route 23 in North Carolina, instanceOf, segment of U.S. Route 23]
-
A.
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.
-
B.
United States federal road
A United States federal road is a roadway that is part of the national highway system and is funded, regulated, or maintained in whole or in part by the federal government to support interstate travel, commerce, and defense.
-
C.
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.
-
D.
Farm to Market Road
A Farm to Market Road is a rural roadway designed to connect agricultural areas and farms with nearby towns, markets, and major transportation routes to facilitate the movement of goods and people.
-
E.
highway segment
chosen
A highway segment is a continuous portion of a highway between two defined endpoints, such as interchanges, intersections, or mile markers, characterized by consistent physical and operational attributes.
- 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_69f34981c54c81909b33c3fa2208a52d |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:41 a.m.