Triple
T8174217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pukapukan language |
E190900
|
entity |
| Predicate | endangeredFactors |
P45185
|
FINISHED |
| Object | outmigration of speakers |
—
|
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: outmigration of speakers | Statement: [Pukapukan language, endangeredFactors, outmigration of speakers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endangeredFactors Context triple: [Pukapukan language, endangeredFactors, outmigration of speakers]
-
A.
areEndangeredIn
Indicates that the entities are classified as endangered within a specified geographic area or jurisdiction.
-
B.
languageEndangermentFactors
chosen
Indicates the various social, political, economic, and cultural conditions that contribute to a language becoming vulnerable, endangered, or extinct.
-
C.
extinctionReason
Indicates the cause or factor responsible for an entity’s extinction.
-
D.
creationCanBecomeExtinct
Indicates that something which has been created is capable of ceasing to exist or becoming extinct.
-
E.
conservationStatus
Indicates the level of risk or protection category assigned to an entity, typically reflecting how threatened it is with extinction or decline.
- 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_69ca82c1c0a08190bf8692b4d91a03ca |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb480a7ac4819088fabd5bec6ba2e5 |
completed | March 31, 2026, 4:05 a.m. |
| PD | Predicate disambiguation | batch_69cb36a4c40c81909f60aef0e1624c13 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:40 p.m.