Triple
T5244847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northwest Caucasian languages |
E118433
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | indigenous languages of the Caucasus |
C2571
|
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: indigenous languages of the Caucasus Context triple: [Northwest Caucasian languages, instanceOf, indigenous languages of the Caucasus]
-
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
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.
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.
-
D.
Indigenous language
chosen
An Indigenous language is a native tongue traditionally spoken by the original inhabitants of a region, embodying their cultural knowledge, identity, and worldview.
-
E.
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.
- 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_69bd4468aacc8190a8196f71855cdf4f |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:49 p.m.