Triple
T13366485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bennebroek |
E318950
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Heemstede |
E80335
|
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: Heemstede | Statement: [Bennebroek, near, Heemstede]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Heemstede Context triple: [Bennebroek, near, Heemstede]
-
A.
Heemstede
chosen
Heemstede is a town and municipality in the province of North Holland in the Netherlands, known as a leafy residential suburb near Haarlem.
-
B.
Deurne
Deurne is a municipality in the Dutch province of North Brabant, known for its rural character and historic peat extraction areas.
-
C.
Deurne
Deurne is a district of the Belgian city of Antwerp, known for its residential neighborhoods and green spaces such as Rivierenhof park.
-
D.
Hulst
Hulst is a historic fortified town and municipality in the Dutch province of Zeeland, near the border with Belgium.
-
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_69d806b7bbac8190b85278c87fa7aff3 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dadcd652d48190a782fd1f57f34b6a |
completed | April 11, 2026, 11:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0883db3d888190a737968796e13f79 |
completed | May 16, 2026, 2:49 p.m. |
Created at: April 9, 2026, 9:32 p.m.