Triple
T17274094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dargic languages |
E419340
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Northeast Caucasian languages |
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 languages Context triple: [Dargic languages, instanceOf, Northeast Caucasian languages]
-
A.
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.
-
B.
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.
-
C.
Uralic language
A Uralic language is a member of the Uralic language family, originating in Northern Eurasia and characterized by features such as agglutinative morphology, extensive case systems, and vowel harmony, including languages like Finnish, Hungarian, and Estonian.
-
D.
Northeast Caucasian people
Northeast Caucasian people are an ethnolinguistic group indigenous to the northeastern Caucasus region, encompassing diverse communities such as Chechens, Avars, and Lezgins who share related Northeast Caucasian languages and cultural traditions.
-
E.
Northwest Caucasian people
Northwest Caucasian people are an indigenous group of ethnic communities native to the northwestern Caucasus region, characterized by distinct languages, cultures, and historical traditions.
- 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:40 a.m.