Triple
T4394026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dixie Highway |
E99438
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic highway network |
C1081
|
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: historic highway network Context triple: [Dixie Highway, instanceOf, historic highway network]
-
A.
historic road
A historic road is a transportation route of significant age and cultural, economic, or political importance, preserved or recognized for its role in shaping historical events, trade, or settlement patterns.
-
B.
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.
-
C.
historic transportation system
chosen
A historic transportation system is an organized network of vehicles, routes, and infrastructure from a past era that once facilitated the movement of people or goods and is now preserved, studied, or remembered for its cultural, technological, or historical significance.
-
D.
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.
-
E.
U.S. Numbered Highway
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.
- 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_69b345506b408190b0e3dee616738a7d |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:20 p.m.