Triple
T26667380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoevelaken |
E672222
|
entity |
| Predicate | roadExit |
P137237
|
FINISHED |
| Object | exits on A1 motorway |
—
|
LITERAL 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: exits on A1 motorway | Statement: [Hoevelaken, roadExit, exits on A1 motorway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadExit Context triple: [Hoevelaken, roadExit, exits on A1 motorway]
-
A.
roadTerminusOf
Indicates that a road ends at, or has its terminal point at, the referenced location or route.
-
B.
exitsThrough
Indicates that an entity leaves or departs from a place, structure, or area by passing through a specified exit or passage.
-
C.
hasStreetExits
chosen
Indicates that a location or structure has one or more exits that lead directly onto a street.
-
D.
roadAccessVia
Indicates that one location or area is reachable from another specifically by using a particular road or road segment.
-
E.
expresswayInterchange
Indicates a road connection where an expressway intersects with another road or expressway, allowing vehicles to transfer between them.
- F. None of above.
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_69eecda00a9c8190b2691f4d89db03b6 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f616c4dda8819088c175f27c5f0961 |
completed | May 2, 2026, 3:22 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:10 a.m.