Triple
T5566882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bilua language |
E145900
|
entity |
| Predicate | isEndangeredBecauseOf |
P6998
|
FINISHED |
| Object | language shift to Solomon Islands Pijin |
—
|
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 Solomon Islands Pijin | Statement: [Bilua language, isEndangeredBecauseOf, language shift to Solomon Islands Pijin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEndangeredBecauseOf Context triple: [Bilua language, isEndangeredBecauseOf, language shift to Solomon Islands Pijin]
-
A.
extinctionReason
chosen
Indicates the cause or factor responsible for an entity’s extinction.
-
B.
areEndangeredIn
Indicates that the entities are classified as endangered within a specified geographic area or jurisdiction.
-
C.
threatenedBy
Indicates that one entity poses a danger or potential harm to another entity.
-
D.
endangerment
Indicates a relationship in which one entity exposes another to potential harm, risk, or danger.
-
E.
creationCanBecomeExtinct
Indicates that something which has been created is capable of ceasing to exist or becoming extinct.
- 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_69c008fdae24819081aa002ad99cd966 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02034fc3081908920c52a19d462e1 |
completed | March 22, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69c01b12826c8190969a584d0f53aa44 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:36 p.m.