Triple
T9450329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honselersdijk |
E227870
|
entity |
| Predicate | roadAccessVia |
P9041
|
FINISHED |
| Object | N222 |
E749328
|
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: N222 | Statement: [Honselersdijk, roadAccessVia, N222]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: N222 Context triple: [Honselersdijk, roadAccessVia, N222]
-
A.
N222
chosen
N222 is a regional road in the Netherlands that connects the town of Wateringen with surrounding areas in the Westland region.
-
B.
N228
N228 is a regional road in the Netherlands that provides access to and from the village of Benschop.
-
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.
N272
N272 is a regional road in the Netherlands that serves as a key connection route in the province of North Brabant, including access to the village of Sint Anthonis.
-
E.
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.
- 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.