Triple

T2208207
Position Surface form Disambiguated ID Type / Status
Subject Areuse E50851 entity
Predicate mouthLocation P417 FINISHED
Object Boudry E136315 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: Boudry | Statement: [Areuse, mouthLocation, Boudry]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Boudry
Context triple: [Areuse, mouthLocation, Boudry]
  • A. Boudry chosen
    Boudry is a municipality in the canton of Neuchâtel in western Switzerland, known as a historic town near Lake Neuchâtel.
  • B. Wavre
    Wavre is a town in central Belgium that serves as the capital of Walloon Brabant and is known for hosting the Walibi Belgium amusement park.
  • C. Bütgenbach
    Bütgenbach is a municipality in eastern Belgium’s German-speaking Community, known for its scenic lake, outdoor recreation, and proximity to the strategic Elsenborn Ridge.
  • D. Michelbeke
    Michelbeke is a village in the municipality of Brakel in East Flanders, Belgium, known for its rural character and cycling-friendly landscape.
  • E. Porrentruy
    Porrentruy is a historic town in northwestern Switzerland known for its medieval castle and role as a regional center in the canton of Jura.
  • 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_69a88b06709c8190978fb2418470d1b6 completed March 4, 2026, 7:41 p.m.
NER Named-entity recognition batch_69abbfcd53b88190991961f103a3e09a completed March 7, 2026, 6:03 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae7efa34e88190a6907515b574f752 completed March 9, 2026, 8:04 a.m.
Created at: March 4, 2026, 7:46 p.m.