Triple
T9450319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honselersdijk |
E227870
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Poeldijk |
E97220
|
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: Poeldijk | Statement: [Honselersdijk, locatedNear, Poeldijk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Poeldijk Context triple: [Honselersdijk, locatedNear, Poeldijk]
-
A.
Poeldijk
chosen
Poeldijk is a village in the Dutch province of South Holland, known for its greenhouse horticulture and proximity to The Hague.
-
B.
Rozenburg
Rozenburg is a town in the western Netherlands that forms part of the heavily industrialized and port-dominated region of South Holland.
-
C.
Rozenburg
Rozenburg is a village in the municipality of Haarlemmermeer in the province of North Holland, Netherlands.
-
D.
Goudswaard
Goudswaard is a small village in the Dutch province of South Holland, known for its rural character and location on the island of Hoeksche Waard.
-
E.
Boesinghe
Boesinghe is a village in West Flanders, Belgium, known for its proximity to key World War I battlefields along the Yser Front.
- 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_69ca8439f8bc8190997f2ef40c9f0bc2 |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7f6649a48190b6844daa6202efe5 |
completed | April 1, 2026, 8:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d12268429c8190bf2fd0f3ea4dac4a |
completed | April 4, 2026, 2:38 p.m. |
Created at: March 30, 2026, 7:51 p.m.