Triple
T24769439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resígaru |
E619679
|
entity |
| Predicate | riskOfExtinction |
P106794
|
FINISHED |
| Object | imminent without intervention |
—
|
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: imminent without intervention | Statement: [Resígaru, riskOfExtinction, imminent without intervention]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riskOfExtinction Context triple: [Resígaru, riskOfExtinction, imminent without intervention]
-
A.
extinctionCertainty
chosen
Indicates the degree of confidence or likelihood that an entity (typically a species or population) will become extinct.
-
B.
impactOfExtinction
Indicates the consequences or effects that the extinction of an entity has on other entities, systems, or conditions.
-
C.
creationCanBecomeExtinct
Indicates that something which has been created is capable of ceasing to exist or becoming extinct.
-
D.
massExtinctionConsequence
Indicates that an event or factor results in, contributes to, or is a direct outcome of a mass extinction event.
-
E.
extinctionReason
Indicates the cause or factor responsible for an entity’s extinction.
- 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_69e2fabd04488190a2d13c97be745a2d |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410a8dc8081909e2f4b65485a6786 |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:29 a.m.