Triple
T3450559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zuid-Beveland |
E72782
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object | Heinkenszand |
E316588
|
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: Heinkenszand | Statement: [Zuid-Beveland, hasSettlement, Heinkenszand]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Heinkenszand Context triple: [Zuid-Beveland, hasSettlement, Heinkenszand]
-
A.
Heinkenszand
chosen
Heinkenszand is a village in the Dutch province of Zeeland that serves as a local center within the South Beveland region.
-
B.
Monnickendam
Monnickendam is a historic fishing town in North Holland, Netherlands, known for its well-preserved old harbor and traditional Dutch architecture.
-
C.
Honselersdijk
Honselersdijk is a village in the Dutch province of South Holland, known for its greenhouse horticulture and proximity to The Hague.
-
D.
Ooijpolder
Ooijpolder is a Dutch riverine polder and nature area near Nijmegen, known for its scenic floodplains, wetlands, and rich birdlife along the Waal River.
-
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_69ad85b05c848190b7a28ceec2bd7b74 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adba7324508190b07943cec3ecdb59 |
completed | March 8, 2026, 6:05 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b37e59178881909facfe90004c9d99 |
completed | March 13, 2026, 3:02 a.m. |
Created at: March 8, 2026, 3:16 p.m.