Triple
T4944701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Species Survival Plan |
E111020
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | population management program |
C15958
|
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: population management program Context triple: [Species Survival Plan, instanceOf, population management program]
-
A.
forest management program
A forest management program is an organized set of policies, practices, and monitoring activities designed to sustainably manage forest resources, balance ecological health with economic and social needs, and ensure long-term forest resilience.
-
B.
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.
-
C.
disease surveillance program
A disease surveillance program is a systematic, ongoing process of collecting, analyzing, and interpreting health data to detect, monitor, and respond to disease occurrences in a population.
-
D.
federal land conservation program
A federal land conservation program is a government-administered initiative that protects, manages, and restores public or private lands to preserve natural resources, biodiversity, and ecosystem services for current and future generations.
-
E.
breeding operation
chosen
A breeding operation is an organized facility or enterprise that manages the controlled reproduction, care, and selection of animals or plants to produce offspring with desired traits.
- 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_69bd441721cc819085c7e33fe0876818 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:31 p.m.