Triple

T22897688
Position Surface form Disambiguated ID Type / Status
Subject Milvignes E568219 entity
Predicate formedByMergerOf P77 FINISHED
Object Boudry NE NERFINISHED

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: [Milvignes, formedByMergerOf, Boudry]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Boudry
Context triple: [Milvignes, formedByMergerOf, 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. Oesling
    Oesling is the sparsely populated, hilly and forested northern region of Luxembourg, forming part of the Ardennes.
  • C. 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.
  • D. Ecaussinnes
    Ecaussinnes is a municipality in the province of Hainaut in Wallonia, Belgium, known for its historic castles and annual folklore festivals.
  • E. Tessenderlo
    Tessenderlo is a municipality in the Belgian province of Limburg, known for its chemical industry and location near the Albert Canal.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e2458c23ec81908fa2570692c6614f completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1801358488190aa2a51f0943ea5bd completed April 29, 2026, 3:50 a.m.
Created at: April 17, 2026, 3:41 p.m.