Triple
T7850634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hellevoetsluis |
E182040
|
entity |
| Predicate | roadConnection |
P385
|
FINISHED |
| Object | N218 |
E354473
|
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: N218 | Statement: [Hellevoetsluis, roadConnection, N218]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: N218 Context triple: [Hellevoetsluis, roadConnection, N218]
-
A.
N218
chosen
N218 is a regional road in the Netherlands that connects the town of Zuidland with other nearby areas in the province of South Holland.
-
B.
N211
N211 is a regional road in the Netherlands that connects several towns and provides important access routes in the South Holland province.
-
C.
N228
N228 is a regional road in the Netherlands that provides access to and from the village of Benschop.
-
D.
N215
N215 is a regional road in the Netherlands that provides access to and connects the village of Nieuwe-Tonge with other parts of the surrounding area.
-
E.
N271
N271 is a regional road in the Netherlands that runs through the province of Limburg, connecting several towns and villages along the Maas river.
- 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_69ca82869ee08190b8f9040dbc2c0467 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb18eaac508190bf373b1d50b52e1e |
completed | March 31, 2026, 12:44 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cb5b0d95748190a202258214dda2ae |
completed | March 31, 2026, 5:26 a.m. |
Created at: March 30, 2026, 4:50 p.m.