Triple
T31997366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonepuri dialect |
E817029
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of Koshali language |
C59952
|
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 Koshali language Context triple: [Sonepuri dialect, instanceOf, variety of Koshali language]
-
A.
variety of the Kati language
A variety of the Kati language is a distinct regional or social form of Kati characterized by its own systematic differences in pronunciation, vocabulary, and sometimes grammar while remaining mutually intelligible with other Kati forms.
-
B.
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.
-
C.
Bhili language variety
A Bhili language variety is a specific regional or social form of the Bhili language, characterized by distinct phonological, lexical, and grammatical features within the broader Bhili linguistic continuum.
-
D.
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.
-
E.
variety of Kodava language
A variety of Kodava language is a distinct regional or social form of Kodava characterized by unique phonological, lexical, or grammatical features within the broader Kodava-speaking community.
- 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_69f348f8ce388190ae84376b1f348f12 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:14 a.m.