Triple
T10987761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avar-Andic languages |
E259673
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Northeast Caucasian language branch |
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 branch Context triple: [Avar-Andic languages, instanceOf, Northeast Caucasian language branch]
-
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.
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.
Kartvelian language branch
The Kartvelian language branch is a small family of closely related languages indigenous to the South Caucasus, including Georgian, Svan, Mingrelian, and Laz, characterized by complex phonology and rich verb morphology.
-
E.
Kartvelian language branch
The Kartvelian language branch is a small family of closely related languages indigenous to the South Caucasus, including Georgian, Svan, Mingrelian, and Laz.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:24 p.m.