Triple
T14420314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | municipality of Hellevoetsluis |
E357565
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Nieuw-Helvoet |
E843715
|
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: Nieuw-Helvoet | Statement: [municipality of Hellevoetsluis, contains, Nieuw-Helvoet]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nieuw-Helvoet Context triple: [municipality of Hellevoetsluis, contains, Nieuw-Helvoet]
-
A.
Nieuw-Helvoet
chosen
Nieuw-Helvoet is a town located on the island of Voorne-Putten in the province of South Holland in the Netherlands.
-
B.
Nieuwenhoorn
Nieuwenhoorn is a village in the western Netherlands that forms part of the province of South Holland.
-
C.
Vollenhoven
Vollenhoven is a Dutch surname most notably associated with philosopher D. H. Th. Vollenhoven, a key figure in Reformational philosophy.
-
D.
Betuwe
Betuwe is a fertile riverine region in the Dutch province of Gelderland, renowned for its extensive fruit orchards and scenic landscapes between the Rhine and Waal rivers.
-
E.
Woudenberg
Woudenberg is a small Dutch municipality and town located in the central Netherlands.
- 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de910eb354819089d5d5a46919eb49 |
completed | April 14, 2026, 7:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd8aa705e08190bff1ab4125bd773f |
completed | May 8, 2026, 7:03 a.m. |
Created at: April 10, 2026, 1:18 a.m.