Triple
T25723636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porcupine Caribou Management Board |
E645056
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | wildlife co-management board |
C38590
|
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: wildlife co-management board Context triple: [Porcupine Caribou Management Board, instanceOf, wildlife co-management board]
-
A.
wildlife management area
A wildlife management area is a designated tract of land or water managed primarily for the conservation, habitat protection, and regulated use of wildlife and natural resources.
-
B.
protected area management body
chosen
A protected area management body is an organization or authority responsible for planning, regulating, and overseeing the conservation, use, and monitoring of a designated protected area and its natural and cultural resources.
-
C.
wildlife refuge
A wildlife refuge is a protected area of land or water managed to conserve native plants, animals, and their habitats while limiting or regulating human activities.
-
D.
co-managed protected area
A co-managed protected area is a conservation zone where responsibility and authority for managing natural resources and biodiversity are shared between government agencies and local communities or other stakeholders through formal agreements.
-
E.
wildlife law enforcement program
A wildlife law enforcement program is an organized governmental or institutional initiative that detects, prevents, and prosecutes violations of wildlife protection laws to conserve species and habitats.
- 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 21, 2026, 10:07 p.m.