Triple
T3596266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiliwa |
E76146
|
entity |
| Predicate | modernChallenges |
P40848
|
FINISHED |
| Object | language loss |
—
|
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 loss | Statement: [Kiliwa, modernChallenges, language loss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernChallenges Context triple: [Kiliwa, modernChallenges, language loss]
-
A.
modernIssue
chosen
Indicates that the subject is a contemporary or current-day issue affecting the object or broader context.
-
B.
modernDevelopment
Indicates that something is associated with or characteristic of recent or contemporary development, progress, or advancement.
-
C.
modernization
Indicates a process by which something is updated, reformed, or transformed to align with contemporary standards, technologies, or practices.
-
D.
modernPractice
Indicates that an entity engages in or reflects a contemporary, up-to-date way of doing something, following current methods, standards, or trends.
-
E.
modernIndustry
Indicates that an entity operates within or is characteristic of contemporary, technologically advanced industrial practices and sectors.
- 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_69ad85d8042081908af94a04c410dec0 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc19b26bc8190b3cc0613a1a98361 |
completed | March 8, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69adb83b66708190bb9d2f23d6fd308e |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:22 p.m.