Triple
T15844338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naukan Yupik language |
E384176
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | indigenous language of Russia |
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 language of Russia Context triple: [Naukan Yupik language, instanceOf, indigenous language of Russia]
-
A.
regional variety of the Russian language
A regional variety of the Russian language is a geographically localized form of Russian characterized by distinctive phonetic, lexical, and sometimes grammatical features that differentiate it from the standard language and other regional forms.
-
B.
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.
-
C.
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.
-
D.
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.
-
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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:50 a.m.