Triple
T33286338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pomor dialects of Russian |
E852188
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety of Russian |
C33033
|
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 Russian Context triple: [Pomor dialects of Russian, instanceOf, regional variety of Russian]
-
A.
regional variety of the Russian language
chosen
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.
Northern Russian dialect
Northern Russian dialect is a group of Russian dialects spoken in the northern regions of European Russia, characterized by conservative phonetic features, distinct vowel pronunciation, and specific lexical and grammatical traits that differ from Standard Russian.
-
C.
Russian dialect
A Russian dialect is a regional or social variety of the Russian language characterized by distinct phonetic, lexical, and grammatical features that differ from the standardized form.
-
D.
regional variety of Votic
A regional variety of Votic is a geographically distinct form of the Votic language characterized by unique phonological, lexical, and grammatical features specific to a particular area or community.
-
E.
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.
- 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_69f349660ff48190a4568803d0b89941 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:32 a.m.