Triple
T31019363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Utah Scenic Byways program |
E790410
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state scenic byway program |
C42446
|
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: state scenic byway program Context triple: [Utah Scenic Byways program, instanceOf, state scenic byway program]
-
A.
scenic highway designation program
chosen
A scenic highway designation program is an initiative that identifies, evaluates, and officially recognizes roadways with exceptional natural, cultural, or historic visual qualities to promote preservation, tourism, and context-sensitive development.
-
B.
scenic byway
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.
-
C.
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.
-
D.
National Park Service roadway segments
National Park Service roadway segments are defined stretches of road within or managed by the National Park Service, used to represent, manage, and analyze the transportation network across park lands.
-
E.
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.
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:58 p.m.