Triple
T1019805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American flamingo |
E22012
|
entity |
| Predicate | conservationThreat |
P584
|
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: [American flamingo, conservationThreat, habitat loss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conservationThreat Context triple: [American flamingo, conservationThreat, habitat loss]
-
A.
threatenedBy
Indicates that one entity poses a danger or potential harm to another entity.
-
B.
conservationIssue
chosen
Indicates that an entity is associated with a problem, threat, or concern related to the protection, preservation, or sustainable management of natural resources or biodiversity.
-
C.
endangerment
Indicates a relationship in which one entity exposes another to potential harm, risk, or danger.
-
D.
conservationFocus
Indicates that the primary emphasis or priority of an entity, project, or action is on conservation-related goals, activities, or outcomes.
-
E.
conservationStatus
Indicates the level of risk or protection category assigned to an entity, typically reflecting how threatened it is with extinction or decline.
- 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_69a493d6e380819097b384986ffc315c |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7dbcf7c8190858b2d16a27bd2ff |
completed | March 1, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69a4b724c7908190a5b92a57fbdbff4e |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.