Triple
T22219960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riemst |
E549181
|
entity |
| Predicate | hasNeighbouringMunicipality |
P224
|
FINISHED |
| Object | Bilzen |
—
|
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: Bilzen | Statement: [Riemst, hasNeighbouringMunicipality, Bilzen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bilzen Context triple: [Riemst, hasNeighbouringMunicipality, Bilzen]
-
A.
Bilzen
chosen
Bilzen is a historic city and municipality in the Belgian province of Limburg, known for its medieval heritage and the nearby Alden Biesen Castle.
-
B.
Velzeke
Velzeke is a village in East Flanders, Belgium, known for its archaeological heritage and status as a sub-municipality of Zottegem.
-
C.
Lembeek
Lembeek is a village in the Belgian municipality of Halle, located along the Senne River in the province of Flemish Brabant.
-
D.
Willebroek
Willebroek is a municipality in northern Belgium known for its canal connections and location between Brussels and Antwerp.
-
E.
Borsbeek
Borsbeek is a small municipality in the Belgian province of Antwerp, known for its suburban character and proximity to the city of Antwerp.
- 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_69e11e403d6481909a94d0aaf157f6ef |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12b8fa3d081908db0a0556b009d8f |
completed | April 28, 2026, 9:50 p.m. |
Created at: April 16, 2026, 8:37 p.m.