Triple
T14159955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jette |
E350909
|
entity |
| Predicate | hasNeighbour |
P5707
|
FINISHED |
| Object | Koekelberg |
E534791
|
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: Koekelberg | Statement: [Jette, hasNeighbour, Koekelberg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Koekelberg Context triple: [Jette, hasNeighbour, Koekelberg]
-
A.
Koekelberg
chosen
Koekelberg is a small municipality in the Brussels-Capital Region of Belgium, known for the National Basilica of the Sacred Heart that dominates its skyline.
-
B.
Schaerbeek
Schaerbeek is a multicultural municipality in the Brussels-Capital Region of Belgium, known for its Art Nouveau architecture and urban character.
-
C.
Kleine-Brogel
Kleine-Brogel is a village in the municipality of Peer in the Belgian province of Limburg, known for hosting a major military air base.
-
D.
Borsbeek
Borsbeek is a small municipality in the Belgian province of Antwerp, known for its suburban character and proximity to the city of Antwerp.
-
E.
Linkebeek
Linkebeek is a small Flemish municipality in the Belgian province of Flemish Brabant, located just south of Brussels.
- 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61393f308190bb357e2bd1916f94 |
completed | April 14, 2026, 3:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcf7f166988190a96d01fb4bd1438e |
completed | May 7, 2026, 8:37 p.m. |
Created at: April 10, 2026, 12:59 a.m.