Triple
T25982241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Zealand sea lion/rāpoka Threat Management Plan |
E646100
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | endangered species recovery plan |
C50409
|
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: endangered species recovery plan Context triple: [New Zealand sea lion/rāpoka Threat Management Plan, instanceOf, endangered species recovery plan]
-
A.
endangered species
An endangered species is a type of organism whose population has declined to a critically low level, placing it at high risk of extinction in the near future.
-
B.
protected area management plan
A protected area management plan is a strategic document that outlines objectives, policies, and actions for conserving biodiversity and managing human use within a designated protected area over a defined period.
-
C.
ecosystem management plan
An ecosystem management plan is a strategic, science-based framework that outlines goals, actions, and monitoring methods to maintain or restore the health, resilience, and sustainability of a specific ecosystem while balancing ecological, social, and economic needs.
-
D.
species of conservation concern
A species of conservation concern is a plant or animal whose population status, trends, or threats indicate it may be at risk and therefore warrants special management, monitoring, or protection efforts.
-
E.
conservation status
Conservation status is a classification that indicates the likelihood that a species or ecosystem will remain extant in the near future, based on factors such as population trends, threats, and habitat conditions.
- F. None of above. chosen
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_69e77e881fc08190ba1c8dc7e2a07f97 |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 22, 2026, 8:54 a.m.