Triple
T14018091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great River Road corridor |
E337252
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | scenic byway corridor |
C8300
|
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: scenic byway corridor Context triple: [Great River Road corridor, instanceOf, scenic byway corridor]
-
A.
scenic byway
chosen
A scenic byway is a designated roadway recognized for its exceptional natural, cultural, historic, or recreational qualities, offering travelers a visually and experientially rich driving route.
-
B.
state scenic corridor
A state scenic corridor is a designated roadway or linear area recognized and protected by a state for its outstanding natural, cultural, or visual qualities, often with special regulations to preserve its scenic character.
-
C.
National Park Service road
A National Park Service road is a designated roadway within or accessing a national park, managed by the National Park Service to provide visitor access while protecting natural and cultural resources.
-
D.
Indigenous travel corridor
An Indigenous travel corridor is a traditional route or network of pathways used by Indigenous peoples for movement, trade, cultural exchange, and connection across their ancestral lands.
-
E.
road transportation corridor
A road transportation corridor is a designated linear area of land that accommodates one or more roadways and associated infrastructure to enable the efficient movement of vehicles, goods, and people between key origins and destinations.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:19 p.m.