Triple

T1456403
Position Surface form Disambiguated ID Type / Status
Subject Cieszyn Silesia E31409 entity
Predicate hasTraditionalDialect P28812 FINISHED
Object Cieszyn Silesian dialect LITERAL FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Cieszyn Silesian dialect | Statement: [Cieszyn Silesia, hasTraditionalDialect, Cieszyn Silesian dialect]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTraditionalDialect
Context triple: [Cieszyn Silesia, hasTraditionalDialect, Cieszyn Silesian dialect]
  • A. hasTraditionalName
    Indicates that an entity is associated with a name traditionally used or recognized for it, often rooted in long-standing cultural or historical practice.
  • B. hasDialectContinuumWith
    Indicates that two languages or dialects are part of a continuous chain of mutually intelligible varieties, without a clear boundary separating them.
  • C. isTraditional
    Indicates that something adheres to long-established customs, practices, or norms rather than modern or innovative ones.
  • D. hasColloquialVariety
    Indicates that one linguistic form, expression, or variety is an informal, colloquial counterpart or version of another.
  • E. hasLinguisticHeritage
    Indicates that one entity possesses or is associated with the linguistic background, tradition, or ancestry of another entity.
  • F. None of above. chosen

Provenance (4 batches)

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_69a49917dfc081909acdbdf5d684f1ef completed March 1, 2026, 7:52 p.m.
NER Named-entity recognition batch_69a4c598b30c8190b87207adf608b89a completed March 1, 2026, 11:02 p.m.
PD Predicate disambiguation batch_69a4c47cdbd0819092022344a2f4ad7b completed March 1, 2026, 10:58 p.m.
PDg Predicate description generation batch_69a4c55508948190922aee3230a4323e completed March 1, 2026, 11:01 p.m.
Created at: March 1, 2026, 8 p.m.