Triple
T24479423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wiawso Sehwi |
E617325
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of the Sehwi language |
C49060
|
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 the Sehwi language Context triple: [Wiawso Sehwi, instanceOf, variety of the Sehwi language]
-
A.
variety of the Seediq language
A variety of the Seediq language is a distinct regional or social form of Seediq characterized by systematic differences in pronunciation, vocabulary, and/or grammar while remaining mutually intelligible with other Seediq forms.
-
B.
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.
-
C.
Yao language variety
A Yao language variety is a specific regional or social form of the Yao language, distinguished by its own characteristic phonological, lexical, and grammatical features within the broader Yao linguistic continuum.
-
D.
Luri language variety
A Luri language variety is a specific regional or social form of the Luri language, distinguished by its own characteristic phonological, lexical, and grammatical features within the broader continuum of Southwestern Iranian dialects.
-
E.
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.
- 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_69e2d7f3ae788190b683394db15f220e |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:21 a.m.