Triple
T7620463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berchem |
E172477
|
entity |
| Predicate | borders |
P224
|
FINISHED |
| Object | Borsbeek |
E692479
|
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: Borsbeek | Statement: [Berchem, borders, Borsbeek]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Borsbeek Context triple: [Berchem, borders, Borsbeek]
-
A.
Borsbeek
chosen
Borsbeek is a small municipality in the Belgian province of Antwerp, known for its suburban character and proximity to the city of Antwerp.
-
B.
Lembeek
Lembeek is a village in the Belgian municipality of Halle, located along the Senne River in the province of Flemish Brabant.
-
C.
Diepenbeek
Diepenbeek is a municipality in the Belgian province of Limburg, known for its blend of residential areas, industry, and the campus of Hasselt University.
-
D.
Linkebeek
Linkebeek is a small Flemish municipality in the Belgian province of Flemish Brabant, located just south of Brussels.
-
E.
Borgerhout
Borgerhout is a densely populated, multicultural district of the Belgian city of Antwerp, known for its vibrant street life and diverse communities.
- 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_69c699506b308190826894dab1d9ea86 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6fa62870c8190b17f44eb7a3ff2ad |
completed | March 27, 2026, 9:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d046ccbe588190a0ba7f276d874825 |
completed | April 3, 2026, 11:01 p.m. |
Created at: March 27, 2026, 3:55 p.m.