Triple

T26489919
Position Surface form Disambiguated ID Type / Status
Subject Vendsyssel dialects E669127 entity
Predicate instanceOf P0 FINISHED
Object regional dialect of Danish C13826 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 Danish
Context triple: [Vendsyssel dialects, instanceOf, regional dialect of Danish]
  • A. Scandinavian dialect chosen
    A Scandinavian dialect is a regional or social variety of a North Germanic language (such as Swedish, Danish, or Norwegian) characterized by distinct pronunciation, vocabulary, and grammar within the Scandinavian region.
  • 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. regional Malay dialect
    A regional Malay dialect is a localized variety of the Malay language characterized by distinct phonological, lexical, and grammatical features shaped by the specific geographic, historical, and cultural context of its speakers.
  • 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. Low German dialect
    A Low German dialect is a regional variety of the West Germanic language continuum spoken mainly in northern Germany and parts of the eastern Netherlands, characterized by distinct phonological, lexical, and grammatical features that differentiate it from High German.
  • 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_69eeb319007081909642b414b114b35a completed April 27, 2026, 12:51 a.m.
Created at: April 27, 2026, 1:02 a.m.