Triple

T2076638
Position Surface form Disambiguated ID Type / Status
Subject Fribourg E44938 entity
Predicate locatedIn P40 FINISHED
Object Romandy E26480 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: [Fribourg, locatedIn, Romandy]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Romandy
Context triple: [Fribourg, locatedIn, Romandy]
  • A. Romandy
    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 chosen
    Romandie is the French-speaking region of western Switzerland, encompassing cantons such as Geneva, Vaud, Neuchâtel, and Jura.
  • D. 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.
  • E. Swiss Germans
    Swiss Germans are a German-speaking ethnic subgroup primarily inhabiting the German-speaking regions of Switzerland, distinguished by their Alemannic dialects and Swiss cultural identity.
  • 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_69a88916c2b48190a5ca2e9b12cad3ed completed March 4, 2026, 7:33 p.m.
NER Named-entity recognition batch_69abba2fa9c48190958826d5226544df completed March 7, 2026, 5:39 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae2734a0688190a43c9687af48d06d completed March 9, 2026, 1:49 a.m.
Created at: March 4, 2026, 7:41 p.m.