Triple
T14620196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tasmania Parks and Wildlife Service |
E343196
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | protected area management agency |
C11266
|
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 area management agency Context triple: [Tasmania Parks and Wildlife Service, instanceOf, protected area management agency]
-
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.
natural resources management agency
chosen
A natural resources management agency is an organization responsible for planning, regulating, and overseeing the sustainable use, conservation, and restoration of natural resources such as land, water, forests, wildlife, and minerals.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69d822dffc3c8190aa173b90761bffda |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:25 a.m.