Triple

T3089137
Position Surface form Disambiguated ID Type / Status
Subject Vaud E64446 entity
Predicate languageRegion P387 FINISHED
Object Romandy E2947 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: Romandy | Statement: [Vaud, languageRegion, Romandy]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Romandy
Context triple: [Vaud, languageRegion, Romandy]
  • A. Romandy chosen
    Romandy is the French-speaking western region of Switzerland, encompassing cantons such as Geneva, Vaud, Neuchâtel, and Jura.
  • B. Lia Rumantscha
    Lia Rumantscha is the main organization dedicated to promoting, standardizing, and preserving the Romansh language in Switzerland.
  • C. Romandie
    Romandie is the French-speaking region of western Switzerland, encompassing cantons such as Geneva, Vaud, Neuchâtel, and Jura.
  • D. Broye–Léman region
    The Broye–Léman region is an administrative district in the canton of Vaud, Switzerland, encompassing several municipalities between the Broye valley and Lake Geneva.
  • E. Franco-Provençal (Arpitan)
    Franco-Provençal (Arpitan) is a Romance language historically spoken in parts of France, Switzerland, and Italy, distinct from both French and Occitan and now considered endangered.
  • 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_69ad857c97d88190b26f9b1c90839c77 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada20b99a4819090c3d3e08ed556ad completed March 8, 2026, 4:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69b1f8a4c1f08190a80efd190e4ed07f completed March 11, 2026, 11:20 p.m.
Created at: March 8, 2026, 3:03 p.m.