Triple
T36849886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rumbur dialect |
E910646
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of Kalasha language |
C64500
|
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 Kalasha language Context triple: [Rumbur dialect, instanceOf, variety of Kalasha language]
-
A.
variety of Koshali language
A variety of Koshali language is a regional or social form of Koshali distinguished by systematic differences in pronunciation, vocabulary, and grammar used by a particular community.
-
B.
variety of the Kalanguya language
A variety of the Kalanguya language is a regional or social form of Kalanguya distinguished by unique phonological, lexical, or grammatical features used by a particular speech community.
-
C.
variety of Burushaski
A variety of Burushaski is a distinct regional or social form of the Burushaski language characterized by unique phonological, lexical, or grammatical features while remaining mutually intelligible with other forms.
-
D.
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.
-
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_69f76e8033d48190a59274f86f13be48 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.