Triple
T13305635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hartekamp estate |
E316928
|
entity |
| Predicate | nearCity |
P350
|
FINISHED |
| Object | Bennebroek |
E318950
|
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: Bennebroek | Statement: [Hartekamp estate, nearCity, Bennebroek]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bennebroek Context triple: [Hartekamp estate, nearCity, Bennebroek]
-
A.
Bennebroek
chosen
Bennebroek is a small town in North Holland, Netherlands, known as one of the country’s smallest former municipalities before merging into Bloemendaal.
-
B.
Neder-Over-Heembeek
Neder-Over-Heembeek is a residential district in the northern part of the Brussels-Capital Region, known for its mix of urban neighborhoods, green spaces, and historical sites.
-
C.
Willebroek
Willebroek is a municipality in northern Belgium known for its canal connections and location between Brussels and Antwerp.
-
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.
Tombeek
Tombeek is a village and sub-municipality of Overijse in the Flemish Brabant province of Belgium.
- 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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d990a76adc8190ab9abcdb79a21ca8 |
completed | April 11, 2026, 12:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f794202df08190acf1a7710b64198c |
completed | May 3, 2026, 6:29 p.m. |
Created at: April 9, 2026, 9:28 p.m.