Triple
T11604804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borgerhout |
E275226
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Berchem |
E172477
|
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: Berchem | Statement: [Borgerhout, borderedBy, Berchem]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Berchem Context triple: [Borgerhout, borderedBy, Berchem]
-
A.
Berchem
chosen
Berchem is a district of the Belgian city of Antwerp, known for its residential neighborhoods, Art Nouveau architecture, and vibrant local culture.
-
B.
Berchem-Sainte-Agathe
Berchem-Sainte-Agathe is a small, predominantly residential municipality in the Brussels-Capital Region of Belgium.
-
C.
Kanegem
Kanegem is a small village in West Flanders, Belgium, known for its historic church and rural character.
-
D.
Cureghem
Cureghem is a historically working-class, multicultural neighborhood in the Brussels municipality of Anderlecht, known for its dense urban fabric and industrial heritage.
-
E.
Michelbeke
Michelbeke is a village in the municipality of Brakel in East Flanders, Belgium, known for its rural character and cycling-friendly landscape.
- 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_69d6aaf84b548190ac072e4fb89ae18f |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d895502e0081909ee9c3d45d26cd91 |
completed | April 10, 2026, 6:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ee87077d008190874a8339b64dd5ec |
completed | April 26, 2026, 9:43 p.m. |
Created at: April 8, 2026, 9:38 p.m.