Triple
T20462026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buynaksk dialect |
E501947
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety of the Kumyk language |
C43564
|
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 Kumyk language Context triple: [Buynaksk dialect, instanceOf, regional variety of the Kumyk language]
-
A.
regional variety of Lezgian
A regional variety of Lezgian is a geographically distinct form of the Lezgian language characterized by unique phonological, lexical, and grammatical features shared by speakers in a particular area.
-
B.
regional variety of Azerbaijani
A regional variety of Azerbaijani is a geographically or socially localized form of the Azerbaijani language characterized by distinct phonological, lexical, and sometimes grammatical features.
-
C.
Dargwa language variety
A Dargwa language variety is a specific regional or social form of the Dargwa language, characterized by distinct phonological, lexical, and grammatical features within the broader Dargwa linguistic continuum.
-
D.
regional variety of the Georgian language
A regional variety of the Georgian language is a geographically or socially localized form of Georgian characterized by distinct phonological, lexical, and sometimes grammatical features while remaining mutually intelligible with the standard language.
-
E.
variety of Lezgian language
A variety of the Lezgian language is a regional or social form of Lezgian distinguished by systematic differences in pronunciation, vocabulary, and sometimes 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_69e0b4ad4940819098cf2ff6413574e5 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:33 a.m.