Triple
T9247464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khwarshi language |
E222232
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Nakh-Daghestanian language |
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: Nakh-Daghestanian language Context triple: [Khwarshi language, instanceOf, Nakh-Daghestanian 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.
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.
Hurro-Urartian language
A Hurro-Urartian language is a member of an extinct family of ancient Near Eastern languages, primarily known from cuneiform inscriptions of the Hurrians and Urartians in the second and first millennia BCE.
-
D.
Tungusic language
A Tungusic language is a member of a small family of agglutinative languages spoken primarily in eastern Siberia, northeastern China, and the Russian Far East by Tungusic peoples.
-
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_69ca841d2b18819089f9faf5b2c2aec0 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:31 p.m.