Triple
T16767966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Defaka language |
E407517
|
entity |
| Predicate | riskOfLanguageLoss |
P99457
|
FINISHED |
| Object | imminent |
—
|
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: imminent | Statement: [Defaka language, riskOfLanguageLoss, imminent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riskOfLanguageLoss Context triple: [Defaka language, riskOfLanguageLoss, imminent]
-
A.
riskOfLanguageShift
chosen
Indicates that there is a likelihood or tendency for one language to be replaced or significantly reduced in use by another within a given community or context.
-
B.
linguisticIsolation
Indicates a condition where an entity is separated from others in terms of language, lacking shared or effective linguistic communication.
-
C.
languageOfDevelopment
Indicates the programming or natural language used to develop, implement, or create a given entity.
-
D.
languageOfEarlyDevelopment
Indicates that a specified language is used during the initial or formative stages of an entity’s development.
-
E.
languageCapacity
Indicates the extent to which an entity is able to understand, produce, or otherwise use language.
- 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_69d8839174188190909f190097207065 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b033d6b88190a1366a58d63b0546 |
completed | April 18, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69e319cbd79c8190a03587a61c18bec0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.