Triple
T11604803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borgerhout |
E275226
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Deurne |
E525348
|
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: Deurne | Statement: [Borgerhout, borderedBy, Deurne]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Deurne Context triple: [Borgerhout, borderedBy, Deurne]
-
A.
Deurne
chosen
Deurne is a district of the Belgian city of Antwerp, known for its residential neighborhoods and green spaces such as Rivierenhof park.
-
B.
Deurne
Deurne is a municipality in the Dutch province of North Brabant, known for its rural character and historic peat extraction areas.
-
C.
Hansweert
Hansweert is a small village in the Dutch province of Zeeland, known historically as a canal and shipping hub along the Western Scheldt.
-
D.
Kortenhoef
Kortenhoef is a village in the Dutch province of North Holland, known for its lakes, peatlands, and scenic natural surroundings.
-
E.
Zwijndrecht
Zwijndrecht is a Dutch town and municipality located in the western Netherlands, known for its position along the rivers near the city of Dordrecht.
- 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_6a00aade82788190a5f3cedbc22065c4 |
completed | May 10, 2026, 3:57 p.m. |
Created at: April 8, 2026, 9:38 p.m.