Triple
T26299510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weda dialect |
E661513
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety of the Sawai language |
C51396
|
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: regional variety of the Sawai language Context triple: [Weda dialect, instanceOf, regional variety of the Sawai language]
-
A.
regional variety of Mandar language
A regional variety of Mandar language is a localized form of the Mandar language distinguished by unique phonological, lexical, and sometimes grammatical features associated with a specific geographic area or community.
-
B.
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.
-
C.
regional variety of Siwu language
A regional variety of the Siwu language is a geographically and socially distinct form of Siwu characterized by systematic differences in pronunciation, vocabulary, and sometimes grammar from other Siwu-speaking areas.
-
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.
regional variety of the Kayan language
A regional variety of the Kayan language is a geographically distinct form of Kayan characterized by unique phonological, lexical, or grammatical features shared by speakers in a particular area.
- 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
Created at: April 26, 2026, 10:14 p.m.