Triple

T16544767
Position Surface form Disambiguated ID Type / Status
Subject Vionnaz E401913 entity
Predicate sharesBorderWith P224 FINISHED
Object Vouvry E1222197 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: Vouvry | Statement: [Vionnaz, sharesBorderWith, Vouvry]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vouvry
Context triple: [Vionnaz, sharesBorderWith, Vouvry]
  • A. Vouvry chosen
    Vouvry is a Swiss municipality in the canton of Valais, located in the Chablais region near the Rhône River and the eastern end of Lake Geneva.
  • B. Veygoux
    Veygoux is a historic estate in the Puy-de-Dôme department of France, best known as the family home of General Louis-Charles-Antoine Desaix and now a museum dedicated to his life and the French Revolution.
  • C. Arbois
    Arbois is a small French town in the Jura region renowned for its vineyards and distinctive Jura wines, particularly vin jaune.
  • D. Villeroux
    Villeroux is a small village in the municipality of Vaux-sur-Sûre in the Walloon region of Belgium.
  • E. Tavigny
    Tavigny is a village in the Walloon region of Belgium, located in the province of Luxembourg.
  • 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_69d88384bc30819084229e7dcdc39a41 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e34560daf08190b353b415d8ab280d completed April 18, 2026, 8:48 a.m.
NED1 Entity disambiguation (via context triple) batch_6a00aae69d1481909f5514cc496f45b5 completed May 10, 2026, 3:57 p.m.
Created at: April 10, 2026, 5:15 a.m.