Triple
T19630904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mortsel |
E471264
|
entity |
| Predicate | hasNeighbouringMunicipality |
P224
|
FINISHED |
| Object | Edegem |
—
|
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: Edegem | Statement: [Mortsel, hasNeighbouringMunicipality, Edegem]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Edegem Context triple: [Mortsel, hasNeighbouringMunicipality, Edegem]
-
A.
Edegem
chosen
Edegem is a municipality in the Belgian province of Antwerp, known as a residential suburb south of the city of Antwerp.
-
B.
Vilvoorde
Vilvoorde is a city in the Flemish Region of Belgium, located just north of Brussels and known as part of the capital’s broader metropolitan area.
-
C.
Roeselare
Roeselare is a city in western Belgium known as an economic and commercial center in the province of West Flanders.
-
D.
Ledegem
Ledegem is a municipality in the Belgian province of West Flanders.
-
E.
Izegem
Izegem is a town in the Belgian province of West Flanders, known historically for its shoe and brush industries.
- 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_69d8e511f28481909f4bc3ea9191e54a |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e641025d708190aa44bb24671b9455 |
completed | April 20, 2026, 3:06 p.m. |
Created at: April 10, 2026, 1:44 p.m.