Triple
T36568506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yukon protected areas network |
E902045
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | system of parks and conservation lands |
C15458
|
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: system of parks and conservation lands Context triple: [Yukon protected areas network, instanceOf, system of parks and conservation lands]
-
A.
conservation lands
Conservation lands are protected areas of land designated to preserve natural resources, biodiversity, and ecosystem functions while often allowing limited, sustainable human use.
-
B.
state park system
A state park system is a coordinated network of publicly managed natural, cultural, and recreational areas within a state, established to conserve resources and provide outdoor recreation and education for the public.
-
C.
protected natural area system
A protected natural area system is an organized network of geographically defined spaces managed through legal or other effective means to conserve biodiversity, ecosystem services, and natural or cultural values over the long term.
-
D.
network of protected areas
chosen
A network of protected areas is a coordinated system of geographically distinct conservation sites managed collectively to maintain biodiversity, ecological processes, and landscape connectivity.
-
E.
national park area
A national park area is a protected geographic region designated by a government to conserve natural landscapes, ecosystems, and wildlife while providing opportunities for public recreation and education.
- 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:11 p.m.