Triple
T3809489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 41 |
E93095
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States Numbered Highway System route |
C491
|
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: United States Numbered Highway System route Context triple: [U.S. Route 41, instanceOf, United States Numbered Highway System route]
-
A.
U.S. Numbered Highway
chosen
A U.S. Numbered Highway is a nationally coordinated, signed roadway within the United States that is part of the United States Numbered Highway System, providing intercity and interstate connections but distinct from the Interstate Highway System.
-
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.
Interstate Highway
An Interstate Highway is a high-capacity, limited-access roadway that forms part of a nationwide network designed to support efficient long-distance and high-speed vehicular travel between major cities and regions.
-
D.
highway system
A highway system is an interconnected network of major roads and supporting infrastructure designed to enable efficient, high-capacity vehicular travel between cities and regions.
-
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.
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_69aed96a60088190ab1df8390fffc935 |
completed | March 9, 2026, 2:30 p.m. |
Created at: March 9, 2026, 3:16 p.m.