Triple
T7620462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berchem |
E172477
|
entity |
| Predicate | borders |
P224
|
FINISHED |
| Object | Mortsel |
E661914
|
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: Mortsel | Statement: [Berchem, borders, Mortsel]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mortsel Context triple: [Berchem, borders, Mortsel]
-
A.
Mortsel
chosen
Mortsel is a municipality in the Belgian province of Antwerp, known as a residential suburb of the city of Antwerp.
-
B.
Edegem
Edegem is a municipality in the Belgian province of Antwerp, known as a residential suburb south of the city of Antwerp.
-
C.
Wommelgem
Wommelgem is a municipality in the Belgian province of Antwerp, known for its suburban character and proximity to the city of Antwerp.
-
D.
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.
-
E.
Roeselare
Roeselare is a city in western Belgium known as an economic and commercial center in the province of West Flanders.
- 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_69ca73246e9c819099fe003f1274523e |
completed | March 30, 2026, 12:57 p.m. |
Created at: March 27, 2026, 3:55 p.m.