Triple
T10510523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper Delaware Scenic and Recreational River |
E247899
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | scenic and recreational river |
C28164
|
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 and recreational river Context triple: [Upper Delaware Scenic and Recreational River, instanceOf, scenic and recreational river]
-
A.
Wild and Scenic River
A Wild and Scenic River is a free-flowing waterway and its adjacent environment that are legally protected to preserve their natural, cultural, and recreational values in an undeveloped condition.
-
B.
National Scenic River
A National Scenic River is a protected waterway designated for its outstanding natural, cultural, and recreational values, preserved in a largely free-flowing and undeveloped condition for public enjoyment and conservation.
-
C.
national river and recreation area
A national river and recreation area is a protected region centered around a significant river and its surrounding lands, managed to conserve natural and cultural resources while providing opportunities for public recreation and education.
-
D.
river corridor
A river corridor is the linear landscape surrounding a river, including its channel, banks, floodplain, and adjacent habitats, through which water, sediment, organisms, and energy flow and interact.
-
E.
riverine sanctuary
A riverine sanctuary is a protected natural area centered around a river and its surrounding ecosystems, preserving aquatic and riparian habitats while supporting biodiversity and sustainable human use.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:27 p.m.