Triple
T1079161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ǀXam |
E23906
|
entity |
| Predicate | endangeredStatusBeforeExtinction |
P19126
|
FINISHED |
| Object | severely endangered |
—
|
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: severely endangered | Statement: [ǀXam, endangeredStatusBeforeExtinction, severely endangered]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endangeredStatusBeforeExtinction Context triple: [ǀXam, endangeredStatusBeforeExtinction, severely endangered]
-
A.
wasOnceNearExtinction
chosen
Indicates that the entity’s population or existence was at one time so low or threatened that it was in serious danger of disappearing entirely.
-
B.
extinctionPeriod
Indicates the time span during which an entity ceases to exist or is considered extinct.
-
C.
conservationStatus
Indicates the level of risk or protection category assigned to an entity, typically reflecting how threatened it is with extinction or decline.
-
D.
extinctionReason
Indicates the cause or factor responsible for an entity’s extinction.
-
E.
areEndangeredIn
Indicates that the entities are classified as endangered within a specified geographic area or jurisdiction.
- 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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b943b41481909b24050ca7e78971 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b73d9f08819093668104f129840e |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.