Triple
T11818531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colorado Scenic and Historic Byways system |
E281064
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | scenic byway system |
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 system Context triple: [Colorado Scenic and Historic Byways system, instanceOf, scenic byway system]
-
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 Scenic Trail
A National Scenic Trail is a federally designated long-distance trail that offers outstanding recreational opportunities and showcases significant natural, scenic, and cultural landscapes across large geographic areas.
-
D.
United States National Historic Trail
A United States National Historic Trail is a federally designated long-distance route that commemorates and protects significant historical travel paths, events, and landscapes across the nation.
-
E.
trail system
A trail system is an interconnected network of designated paths and routes designed to guide users through natural or built environments for recreation, transportation, or exploration.
- 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:42 p.m.