Triple
T15100660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krakolye dialect |
E360654
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variety of Votic |
C35441
|
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 Votic Context triple: [Krakolye dialect, instanceOf, regional variety of Votic]
-
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.
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.
-
C.
Surmic language
A Surmic language is any member of a subgroup of the Eastern Sudanic branch of the Nilo-Saharan language family, spoken primarily in southwestern Ethiopia and neighboring regions of South Sudan.
-
D.
Baltic German
A Baltic German is a member of the historically German-speaking minority that lived in the Baltic region (primarily present-day Estonia and Latvia), often forming part of the local urban elite and nobility from medieval times until the 20th century.
-
E.
South Estonian dialect
The South Estonian dialect is a group of Finnic language varieties spoken in southern Estonia, distinct from Standard Estonian in phonology, grammar, and vocabulary, and often considered a separate language by linguists.
- F. None of above. chosen
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_69d85a0491ec8190830960be8fafb994 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:04 a.m.