Triple
T33236985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle Fork Clearwater River |
E850853
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | wild and scenic river |
C22205
|
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: wild and scenic river Context triple: [Middle Fork Clearwater River, instanceOf, wild and scenic river]
-
A.
Wild and Scenic River
chosen
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 Scenic Riverway
A National Scenic Riverway is a protected river corridor designated for its outstanding natural, cultural, and recreational values, managed to preserve its free-flowing condition and scenic character for public enjoyment and conservation.
-
D.
scenic and recreational river
A scenic and recreational river is a naturally flowing waterway and its adjacent lands that are preserved for their outstanding natural beauty, ecological value, and opportunities for outdoor activities such as boating, fishing, and hiking.
-
E.
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.
- 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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:31 a.m.