Triple

T16448538
Position Surface form Disambiguated ID Type / Status
Subject Val Venosta E399493 entity
Predicate hasMinorityLanguage P2267 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: [Val Venosta, hasMinorityLanguage, Ladin]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ladin
Context triple: [Val Venosta, hasMinorityLanguage, 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. Luganese
    Luganese is a region in the southern part of the Swiss canton of Ticino centered around the city of Lugano.
  • 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_69d87f2c6778819080fcfae53be8f12a completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e32cdee44c8190ae0df20c58ff7558 completed April 18, 2026, 7:03 a.m.
NED1 Entity disambiguation (via context triple) batch_6a004594a4508190be08f3acfff36ab0 completed May 10, 2026, 8:45 a.m.
Created at: April 10, 2026, 5:10 a.m.