Triple
T10150714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sommelsdijk |
E232628
|
entity |
| Predicate | roadAccessVia |
P9041
|
FINISHED |
| Object | N215 |
E454758
|
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: N215 | Statement: [Sommelsdijk, roadAccessVia, N215]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: N215 Context triple: [Sommelsdijk, roadAccessVia, N215]
-
A.
N215
chosen
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.
-
B.
N213
N213 is a regional road in the Netherlands that provides key access to the Westland area, including the town of Honselersdijk.
-
C.
N211
N211 is a regional road in the Netherlands that connects several towns and provides important access routes in the South Holland province.
-
D.
N218
N218 is a regional road in the Netherlands that connects the town of Zuidland with other nearby areas in the province of South Holland.
-
E.
N222
N222 is a regional road in the Netherlands that connects the town of Wateringen with surrounding areas in the Westland region.
- 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_69ca84885e48819088a31b127cf44904 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec0584a48190b65daa8370555c27 |
completed | April 2, 2026, 4:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2e640d1e0819094d30556ccb958b0 |
completed | April 5, 2026, 10:46 p.m. |
Created at: March 30, 2026, 9:08 p.m.