Triple
T19877767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Scenic Highway System (in designated segments) |
E477684
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | scenic highway designation 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: scenic highway designation program Context triple: [State Scenic Highway System (in designated segments), instanceOf, scenic highway designation program]
-
A.
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.
-
B.
trail designation program
A trail designation program is a structured process used to evaluate, classify, and officially recognize specific routes or paths for designated recreational, conservation, or transportation purposes.
-
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 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.
-
E.
trail designation
A trail designation is a label or classification assigned to a trail that defines its permitted uses, difficulty level, regulatory status, and other management or user information.
- F. None of above. chosen
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_69d8e51f32b08190b3687f4f60353250 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:52 p.m.