Triple
T15556752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Komi-Permyak language |
E370889
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Permic language |
C3812
|
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: Permic language Context triple: [Komi-Permyak language, instanceOf, Permic language]
-
A.
Uralic language
chosen
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.
-
B.
Finnic language
A Finnic language is a member of the Uralic language family spoken primarily around the Baltic Sea region, including languages such as Finnish, Estonian, and Karelian, characterized by agglutinative morphology and vowel harmony.
-
C.
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.
-
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.
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.
- 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_69d85cc6cf40819091f4a5facee1ebe6 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 4:09 a.m.