Triple
T19471872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuba dialect |
E487141
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of Lezgian language |
C42060
|
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 Lezgian language Context triple: [Kuba dialect, instanceOf, variety of Lezgian language]
-
A.
variety of Ossetian language
A variety of Ossetian language is a distinct regional or social form of Ossetian characterized by specific phonological, lexical, and grammatical features within the broader Ossetian linguistic continuum.
-
B.
variety of Gorani language
A variety of Gorani language is a regional or social form of the Gorani speech continuum, distinguished by its own phonological, lexical, and grammatical features while remaining mutually intelligible with other Gorani varieties.
-
C.
variety of the Uzbek language
A variety of the Uzbek language is a regionally or socially distinct form of Uzbek characterized by unique phonological, lexical, and grammatical features while remaining mutually intelligible with other forms.
-
D.
variety of Tajik language
A variety of Tajik language is a regional or social form of Tajik distinguished by specific phonological, lexical, and grammatical features while remaining mutually intelligible with other forms of Tajik.
-
E.
variety of the Tatar language
A variety of the Tatar language is a regionally or socially distinct form of Tatar characterized by specific phonological, lexical, and grammatical features while remaining mutually intelligible with other Tatar 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_69d8e8d924388190b847cb15bb3d0aff |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:39 p.m.