Triple

T22198135
Position Surface form Disambiguated ID Type / Status
Subject Dolomite Ladin varieties E548600 entity
Predicate hasDialect P4251 FINISHED
Object Gherdëina Ladin NE NERFINISHED

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: Gherdëina Ladin | Statement: [Dolomite Ladin varieties, hasDialect, Gherdëina Ladin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gherdëina Ladin
Context triple: [Dolomite Ladin varieties, hasDialect, Gherdëina Ladin]
  • A. Gröden Ladin
    Gröden Ladin is the Ladin language variety spoken in the Val Gardena (Gherdëina) region of the Dolomites in northern Italy.
  • B. Ladin language
    Ladin language is a Rhaeto-Romance language spoken primarily in the Dolomite mountain region of northern Italy.
  • C. Savognin
    Savognin is a Swiss mountain village and ski resort in the canton of Graubünden, known for its alpine scenery and outdoor recreation.
  • D. Valtellinese
    Valtellinese is a regional variety of the Lombard language spoken in the Valtellina valley of northern Italy.
  • E. Gherdëina chosen
    Gherdëina is a Ladin dialect spoken in the Val Gardena region of the Dolomites in northern Italy.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e11e3ecc7c8190b5f94cd8f42e9d37 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f12ae8c74c819080c7f9e8383ecaa7 completed April 28, 2026, 9:47 p.m.
Created at: April 16, 2026, 8:36 p.m.