Triple
T4844245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | black-footed ferret recovery program |
E108250
|
entity |
| Predicate | threatAddressed |
P19863
|
FINISHED |
| Object | habitat loss |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: habitat loss | Statement: [black-footed ferret recovery program, threatAddressed, habitat loss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threatAddressed Context triple: [black-footed ferret recovery program, threatAddressed, habitat loss]
-
A.
threatTypeAddressed
chosen
Indicates that a given action, measure, or entity is specifically intended to counter or mitigate a particular type of threat.
-
B.
threatType
Indicates the specific category or nature of a threat that one entity poses or represents in relation to another.
-
C.
threatStatus
Indicates the level or category of risk or danger posed by one entity to another or to a defined system or environment.
-
D.
threatCategory
Indicates the classification of a threat according to its type, severity, or nature within a defined risk or security framework.
-
E.
riskAddressed
Indicates that a particular risk has been identified and is being mitigated, managed, or otherwise handled by an associated action, control, or measure.
- F. None of above.
Provenance (3 batches)
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_69bd4409b264819085ab855f3eb5381a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e01872c81909607010c10538ad1 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2375a4819098e16acb982c8fab |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:25 p.m.