Triple
T27022478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skaw Karen |
E680702
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of Sgaw Karen language |
C52390
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: variety of Sgaw Karen language Context triple: [Skaw Karen, instanceOf, variety of Sgaw Karen language]
-
A.
variety of the Kayan language
A variety of the Kayan language is a distinct regional or social form of Kayan characterized by its own phonological, lexical, and grammatical features while remaining mutually intelligible to varying degrees with other Kayan varieties.
-
B.
variety of Kunama language
A variety of Kunama language is a distinct regional or social form of the Kunama language characterized by unique phonological, lexical, or grammatical features within the broader Kunama-speaking community.
-
C.
variety of Siwu language
A variety of the Siwu language is a distinct regional or social form of Siwu characterized by systematic differences in pronunciation, vocabulary, or grammar while remaining mutually intelligible with other forms.
-
D.
variety of the Kaili language
A variety of the Kaili language is a distinct regional or social form of Kaili characterized by unique phonological, lexical, or grammatical features while remaining mutually intelligible with other Kaili forms.
-
E.
variety of the Karbi language
A variety of the Karbi language is a distinct regional or social form of Karbi characterized by systematic differences in pronunciation, vocabulary, or grammar while remaining mutually intelligible with other forms.
- F. None of above. chosen
Provenance (1 batch)
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_69eeeb5450988190bfc9a3c012ac463a |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 27, 2026, 7:09 a.m.