Triple
T8527690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilrijk |
E201858
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Aartselaar |
E692457
|
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: Aartselaar | Statement: [Wilrijk, near, Aartselaar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aartselaar Context triple: [Wilrijk, near, Aartselaar]
-
A.
Aartselaar
chosen
Aartselaar is a municipality in the Belgian province of Antwerp, known for its residential character and proximity to the city of Antwerp.
-
B.
Roeselare
Roeselare is a city in western Belgium known as an economic and commercial center in the province of West Flanders.
-
C.
Borgerhout
Borgerhout is a densely populated, multicultural district of the Belgian city of Antwerp, known for its vibrant street life and diverse communities.
-
D.
Lembeek
Lembeek is a village in the Belgian municipality of Halle, located along the Senne River in the province of Flemish Brabant.
-
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 (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_69ca83228b24819085d22e7dc99f5d94 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe6477100819081fa20cb6b8ea3d7 |
completed | March 31, 2026, 3:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d100a931988190aaff56f16057ea90 |
completed | April 4, 2026, 12:14 p.m. |
Created at: March 30, 2026, 6:17 p.m.