Triple
T1633655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California condor recovery program |
E35315
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | endangered species management initiative |
C2976
|
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 management initiative Context triple: [California condor recovery program, instanceOf, endangered species management initiative]
-
A.
biodiversity conservation initiative
chosen
A biodiversity conservation initiative is a coordinated effort or program designed to protect, restore, and sustainably manage the variety of life in ecosystems, species, and genetic resources within a defined area or context.
-
B.
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.
-
C.
global conservation initiative
A global conservation initiative is a coordinated, international effort that unites governments, organizations, and communities to protect biodiversity, restore ecosystems, and promote sustainable use of natural resources worldwide.
-
D.
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.
-
E.
international conservation status
International conservation status is a classification that indicates the level of risk of extinction faced by a species or ecosystem globally, based on standardized scientific criteria and assessments.
- 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_69a886036bc081909ff5de16dbe5e8ea |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:28 p.m.