Triple

T11091227
Position Surface form Disambiguated ID Type / Status
Subject Brunico E262258 entity
Predicate hasRecognizedLanguage P238 FINISHED
Object Ladin E23172 NE 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: Ladin | Statement: [Brunico, hasRecognizedLanguage, Ladin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ladin
Context triple: [Brunico, hasRecognizedLanguage, Ladin]
  • A. Ladinian
    The Ladinian is a Middle Triassic geologic age and stage characterized by significant marine sedimentation and the diversification of early Mesozoic life.
  • B. Ladin language chosen
    Ladin language is a Rhaeto-Romance language spoken primarily in the Dolomite mountain region of northern Italy.
  • C. Segestani
    The Segestani were an ancient Illyrian tribe that inhabited the region around the city of Siscia in what is now central Croatia.
  • D. 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.
  • E. Ladin people
    The Ladin people are a Rhaeto-Romance ethnic group native to the Dolomite mountain region of northern Italy, known for their distinct Ladin language and alpine cultural traditions.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d6aa9a40d88190a373e2c7e48285db completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d799ebae8c8190987b474adb7ede47 completed April 9, 2026, 12:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69e3e7c586808190a576803b7406a49e completed April 18, 2026, 8:21 p.m.
Created at: April 8, 2026, 9:27 p.m.