Triple
T27052845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wild Forest |
E684821
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Adirondack Park land-use category |
C6998
|
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: Adirondack Park land-use category Context triple: [Wild Forest, instanceOf, Adirondack Park land-use category]
-
A.
Adirondack Forest Preserve unit
An Adirondack Forest Preserve unit is a designated tract of public land within New York’s Adirondack Park that is legally protected to remain “forever wild,” managed for conservation, recreation, and ecological integrity.
-
B.
tract of Adirondack Forest Preserve
A tract of Adirondack Forest Preserve is a legally protected parcel of forested land within New York’s Adirondack Park that is constitutionally safeguarded as “forever wild,” prohibiting its sale, lease, or development.
-
C.
protected area designation in the United States
chosen
A protected area designation in the United States is an official legal or administrative status applied to lands and waters to conserve natural, cultural, or recreational resources by regulating their use and development.
-
D.
New York State park
A New York State park is a publicly managed natural or recreational area within New York State that preserves environmental, historical, or cultural resources while providing outdoor activities and amenities for visitors.
-
E.
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.
- 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_69ef14829fac8190914bef9ecc3005d7 |
completed | April 27, 2026, 7:47 a.m. |
Created at: April 27, 2026, 8:15 a.m.