Triple
T31456125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Connecticut scenic roads |
E802454
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | scenic road 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 road program Context triple: [Connecticut scenic roads, instanceOf, scenic road 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.
scenic forest road
A scenic forest road is a winding pathway that cuts through dense woodland, offering picturesque views of trees, foliage, and natural landscapes along its route.
-
D.
scenic coastal road
A scenic coastal road is a winding route that follows the shoreline, offering travelers expansive views of the ocean, cliffs, beaches, and surrounding natural landscapes.
-
E.
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.
- 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_69f348c678ac81908a2e950867619061 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 9:16 p.m.