Triple
T16821806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Driehuis |
E408911
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Santpoort-Zuid |
E963812
|
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: Santpoort-Zuid | Statement: [Driehuis, locatedNear, Santpoort-Zuid]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Santpoort-Zuid Context triple: [Driehuis, locatedNear, Santpoort-Zuid]
-
A.
Santpoort-Noord
Santpoort-Noord is a village in the Dutch province of North Holland, situated within the municipality of Velsen near the North Sea coast.
-
B.
Santpoort
chosen
Santpoort is a village in the Dutch province of North Holland, known for its historic estates, dunes, and proximity to the city of Haarlem.
-
C.
Zuidwijk
Zuidwijk is a neighborhood located within the IJsselmonde district of Rotterdam in the Netherlands.
-
D.
Poortvliet
Poortvliet is a village in the Dutch province of Zeeland, located on the island of Tholen.
-
E.
Bezuidenhout
Bezuidenhout is a neighborhood in The Hague, Netherlands, known for its residential character and proximity to major government and business districts.
- 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b2e77ab88190be1ec8179251864e |
completed | April 18, 2026, 4:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00bb11f8708190ae762a28710e4246 |
completed | May 10, 2026, 5:06 p.m. |
Created at: April 10, 2026, 5:23 a.m.