Triple
T13311222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon Wilderness Act of 1984 |
E317069
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | wilderness legislation |
C21409
|
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 legislation Context triple: [Oregon Wilderness Act of 1984, instanceOf, wilderness legislation]
-
A.
wilderness protection law
chosen
Wilderness protection law is a body of legal rules and regulations designed to preserve natural areas in their undeveloped state by restricting human activities that could degrade their ecological, scenic, or recreational values.
-
B.
federal wilderness area
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.
-
C.
wildlife protection law
A wildlife protection law is a legal framework that regulates human activities to conserve wild animal and plant species, their habitats, and biodiversity, often through prohibitions, permits, and enforcement mechanisms.
-
D.
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.
-
E.
wildlife conservation law
Wildlife conservation law is the body of legal rules, regulations, and policies designed to protect wild animal species and their habitats, manage human impacts on ecosystems, and promote biodiversity for present and future generations.
- 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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:29 p.m.