Triple
T15127144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Karelian |
E361319
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety of the Karelian language |
C3813
|
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 Karelian language Context triple: [South Karelian, instanceOf, regional variety of the Karelian language]
-
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.
Finnish dialect
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.
-
C.
Finnic language
chosen
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.
-
D.
regional variety of Polish
A regional variety of Polish is a geographically localized form of the Polish language characterized by distinct pronunciation, vocabulary, and sometimes grammar that reflect the cultural and historical influences of a specific area.
-
E.
Baltic language
A Baltic language is a member of the Indo-European language family spoken primarily around the eastern coast of the Baltic Sea, characterized by conservative grammatical features and rich inflectional 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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:06 a.m.