Triple
T2569972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mingrelian language |
E57640
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | South Caucasian language |
C8799
|
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: South Caucasian language Context triple: [Mingrelian language, instanceOf, South Caucasian language]
-
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.
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.
-
C.
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.
-
D.
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.
-
E.
Kartvelian language
chosen
A Kartvelian language is a member of a small family of indigenous languages of the South Caucasus, including Georgian, Svan, Mingrelian, and Laz, characterized by complex phonology and morphology and no proven genetic relation to other language families.
- 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_69ab4a51410081908501dcf8bad9adc4 |
completed | March 6, 2026, 9:42 p.m. |
Created at: March 6, 2026, 9:48 p.m.