Triple
T12658345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulch language |
E302346
|
entity |
| Predicate | isEndangeredDueTo |
P106049
|
FINISHED |
| Object | language shift to Russian |
—
|
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: language shift to Russian | Statement: [Ulch language, isEndangeredDueTo, language shift to Russian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEndangeredDueTo Context triple: [Ulch language, isEndangeredDueTo, language shift to Russian]
-
A.
areEndangeredIn
Indicates that the entities are classified as endangered within a specified geographic area or jurisdiction.
-
B.
areEndangeredOrVulnerable
Indicates that the entities are classified as being at risk of extinction, either endangered or vulnerable, according to conservation status criteria.
-
C.
hasConservationConcernIn
Indicates that an entity is subject to a specified conservation concern status within a particular geographic area or jurisdiction.
-
D.
threatenedBy
Indicates that one entity poses a danger or potential harm to another entity.
-
E.
areEndangeredInPart
Indicates that an entity is endangered only in certain regions or parts of its overall range, rather than throughout its entire distribution.
- F. None of above. chosen
Provenance (4 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_69d7bded71a88190bb76e2413af9ea66 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617b07ec8190b714f04ae6654060 |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b78ce8819091f15dd5013e6da5 |
completed | April 10, 2026, 8:42 p.m. |
| PDg | Predicate description generation | batch_69d96179c7648190a05a13991d62bebb |
completed | April 10, 2026, 8:45 p.m. |
Created at: April 9, 2026, 5:19 p.m.