Triple
T20720528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Columbia provincial parks system |
E509298
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | protected areas system |
C29446
|
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: protected areas system Context triple: [British Columbia provincial parks system, instanceOf, protected areas system]
-
A.
network of protected areas
A network of protected areas is a coordinated system of geographically distinct conservation sites managed collectively to maintain biodiversity, ecological processes, and landscape connectivity.
-
B.
protected natural area system
chosen
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.
-
C.
Protected area designation
A protected area designation is an official classification assigned to a geographic region to conserve its natural, cultural, or ecological values by regulating human activities and land use.
-
D.
protected areas database
A protected areas database is a structured repository that stores, organizes, and provides access to information about designated conservation sites, including their locations, legal status, management, and ecological characteristics.
-
E.
protected area designation in the United States
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.
- 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_69e0b4c4cc648190b45fda6e2b20af56 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:26 p.m.