Triple

T17750371
Position Surface form Disambiguated ID Type / Status
Subject Podhale dialect of Polish E443096 entity
Predicate instanceOf P0 FINISHED
Object regional dialect of Polish C30381 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 dialect of Polish
Context triple: [Podhale dialect of Polish, instanceOf, regional dialect of Polish]
  • A. regional variety of Polish chosen
    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.
  • B. Slavic dialect
    A Slavic dialect is a regional or social variety of a Slavic language characterized by distinct phonological, grammatical, and lexical features that differentiate it from the standard language and other dialects.
  • C. 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.
  • D. Slovak dialects
    Slovak dialects are regional varieties of the Slovak language that differ in pronunciation, vocabulary, and grammar across various parts of Slovakia and neighboring Slovak-speaking communities.
  • E. West Slavic languages
    West Slavic languages are a subgroup of the Slavic language family, including Polish, Czech, Slovak, and related languages, primarily spoken in Central Europe and characterized by shared phonological, grammatical, and lexical features.
  • 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 completed April 10, 2026, 8:50 a.m.
Created at: April 10, 2026, 10:10 a.m.