Triple
T29980053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Mexico Scenic and Recreational River (upper reaches) |
E761561
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 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: recreational river Context triple: [New Mexico Scenic and Recreational River (upper reaches), instanceOf, recreational river]
-
A.
scenic and recreational river
chosen
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.
-
B.
river rapids
River rapids are fast-flowing, turbulent sections of a river where water rushes over obstacles and steep gradients, creating waves, eddies, and whitewater.
-
C.
whitewater recreation area
A whitewater recreation area is a designated natural or artificial river section engineered or managed to provide safe, accessible environments for activities like rafting, kayaking, and canoeing in fast-moving, turbulent water.
-
D.
river
A river is a natural flowing body of water, usually freshwater, that moves continuously along a defined channel from higher elevations toward lower ones, often emptying into a sea, lake, or another river.
-
E.
recreational dam
A recreational dam is a structure built across a waterway primarily to create and manage water bodies for leisure activities such as boating, fishing, and swimming, rather than for industrial, agricultural, or hydroelectric purposes.
- 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_69f2246851148190b8e76206db94b105 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:34 p.m.