Triple
T8950753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sankt Vith canton |
E213339
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Bütgenbach |
E58777
|
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: Bütgenbach | Statement: [Sankt Vith canton, contains, Bütgenbach]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bütgenbach Context triple: [Sankt Vith canton, contains, Bütgenbach]
-
A.
Bütgenbach
chosen
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.
-
B.
Buizingen
Buizingen is a village and suburb of Halle in Flemish Brabant, Belgium, known in part for the 2010 train collision that occurred near its railway station.
-
C.
Ottignies
Ottignies is a town in central Belgium, in Walloon Brabant, known as a regional transport hub on the rail route between Brussels and Namur.
-
D.
Verviers
Verviers is a city in eastern Belgium known historically for its textile industry and as a regional center in the province of Liège.
-
E.
Bottendorf
Bottendorf is a locality in the German state of Thuringia that historically existed within the German Empire.
- 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_69ca839843408190a39069a029a89f15 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc670c7244819084978922a9835bc9 |
completed | April 1, 2026, 12:30 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfc93c678c81909d2ab68308d7c2f0 |
completed | April 3, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:59 p.m.