Triple
T17526271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Molenaarsgraaf |
E426802
|
entity |
| Predicate | roadAccess |
P385
|
FINISHED |
| Object | N214 |
—
|
NE NERFINISHED |
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: N214 | Statement: [Molenaarsgraaf, roadAccess, N214]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: N214 Context triple: [Molenaarsgraaf, roadAccess, N214]
-
A.
N214
chosen
N214 is a regional road in the Netherlands that provides a key connection to the village of Hoornaar and surrounding areas.
-
B.
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.
-
C.
N224
N224 is a regional road in the Netherlands that connects several towns and provides important access to and from Renswoude.
-
D.
N211
N211 is a regional road in the Netherlands that connects several towns and provides important access routes in the South Holland province.
-
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 (2 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_69d889de677081909b22d2657b1f0292 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e452d6a2548190acf26f2d5d4aab66 |
completed | April 19, 2026, 3:58 a.m. |
Created at: April 10, 2026, 5:49 a.m.