Triple
T21666897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uma’ Pawe language |
E534744
|
entity |
| Predicate | isUnderThreatFrom |
P956
|
FINISHED |
| Object | dominance of Indonesian |
—
|
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: dominance of Indonesian | Statement: [Uma’ Pawe language, isUnderThreatFrom, dominance of Indonesian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUnderThreatFrom Context triple: [Uma’ Pawe language, isUnderThreatFrom, dominance of Indonesian]
-
A.
threatenedBy
chosen
Indicates that one entity poses a danger or potential harm to another entity.
-
B.
isThreatenedCategory
Indicates that an entity belongs to a category facing risk of harm, decline, or extinction.
-
C.
hasThreats
Indicates that one entity poses or is associated with potential danger, harm, or adverse consequences toward another entity.
-
D.
underDangerList
Indicates that an entity is classified as being on a designated danger or endangered list, signifying it is at risk or under threat.
-
E.
perceivedThreat
Indicates that one entity regards another entity or situation as potentially harmful, dangerous, or adverse.
- 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_69e0c46898008190aa618a4af55bd1ee |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef6c0c236881909ffaefea8601b1c2 |
completed | April 27, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69e6968abfdc81909cf9e0bd72db9eca |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:37 p.m.