Triple
T14401389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Varanger Kven |
E357078
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety of the Kven language |
C25355
|
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: regional variety of the Kven language Context triple: [Varanger Kven, instanceOf, regional variety of the Kven language]
-
A.
Yana language variety
Yana language variety refers to any of the related but distinct forms of the Yana language traditionally spoken by the Yana people of northern California, encompassing dialectal differences in phonology, vocabulary, and grammar.
-
B.
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.
-
C.
Finnish dialect
chosen
A Finnish dialect is a regional or social variety of the Finnish language characterized by distinct pronunciation, vocabulary, and grammatical features that differ from the standardized form and other dialects.
-
D.
Yup'ik language variety
A Yup'ik language variety is a specific regional or social form of the Yup'ik language distinguished by its unique phonological, lexical, and grammatical features within the broader Yup'ik linguistic continuum.
-
E.
regional variety of Kikuyu language
A regional variety of the Kikuyu language is a geographically defined form of Kikuyu characterized by distinct phonological, lexical, and sometimes grammatical features shared by speakers in a particular area.
- 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:17 a.m.