Triple
T33357871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frank Church–River of No Return Wilderness (small portions nearby region) |
E854124
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | wilderness area segment |
C23681
|
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: wilderness area segment Context triple: [Frank Church–River of No Return Wilderness (small portions nearby region), instanceOf, wilderness area segment]
-
A.
wilderness study area
A wilderness study area is a region of public land identified and managed for its natural, undeveloped character while being evaluated for potential permanent wilderness designation.
-
B.
wildland area
A wildland area is a largely undeveloped, natural landscape managed to preserve its ecological integrity, native biodiversity, and opportunities for primitive recreation with minimal human impact.
-
C.
wilderness preserve
A wilderness preserve is a protected natural area set aside to conserve ecosystems, wildlife, and landscapes in an undisturbed or minimally impacted state, often limiting human activities to low-impact recreation and scientific study.
-
D.
federal wilderness area
chosen
A federal wilderness area is a region of public land designated and protected by the government to preserve its natural conditions, where human activities and development are highly restricted to maintain its wilderness character.
-
E.
wildland park
A wildland park is a protected natural area managed primarily to conserve ecosystems and wildlife while providing low-impact recreational opportunities in a largely undeveloped landscape.
- 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_69f3496acbc8819099fd0305ecc42080 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:34 a.m.