Triple
T19332984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kubachi |
E483542
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Northeast Caucasian language variety |
C14524
|
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: Northeast Caucasian language variety Context triple: [Kubachi, instanceOf, Northeast Caucasian language variety]
-
A.
Northeast Caucasian language
chosen
A Northeast Caucasian language is a member of a diverse family of languages spoken primarily in the northeastern Caucasus region, characterized by complex consonant systems and rich case morphology.
-
B.
Northwest Caucasian language
A Northwest Caucasian language is a member of a small family of indigenous languages spoken in the northwestern Caucasus region, characterized by complex consonant systems, minimal vowel inventories, and rich verbal morphology.
-
C.
Afroasiatic language variety
An Afroasiatic language variety is a specific form or dialect of a language belonging to the Afroasiatic family, characterized by shared structural features and historical origins across regions of North Africa, the Horn of Africa, and parts of the Middle East.
-
D.
Turkic–Iranian mixed language
A Turkic–Iranian mixed language is a contact language that combines core grammatical and lexical features from both Turkic and Iranian language families, typically arising in regions where their speaker communities have long coexisted.
-
E.
Gumuz language variety
A Gumuz language variety is a specific form or dialect of the Gumuz language, distinguished by its unique phonological, lexical, or grammatical features within the broader Gumuz linguistic continuum.
- F. None of above.
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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:33 p.m.