Triple
T26527108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aknogai dialect |
E670721
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of the Nogai language |
C51706
|
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 the Nogai language Context triple: [Aknogai dialect, instanceOf, variety of the Nogai language]
-
A.
variety of the Isnag language
A variety of the Isnag language is a regional or social form of Isnag distinguished by systematic differences in pronunciation, vocabulary, or grammar while remaining mutually intelligible with other forms.
-
B.
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.
-
C.
variety of Avar language
A variety of Avar language is a regional or social form of the Avar language distinguished by unique phonological, lexical, or grammatical features while remaining mutually intelligible with other Avar forms.
-
D.
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.
-
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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
Created at: April 27, 2026, 1:32 a.m.