Triple
T27395336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A28 motorway |
E691665
|
entity |
| Predicate | hasRoadMarkingStandard |
P142975
|
FINISHED |
| Object | Dutch road marking standard |
—
|
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: Dutch road marking standard | Statement: [A28 motorway, hasRoadMarkingStandard, Dutch road marking standard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadMarkingStandard Context triple: [A28 motorway, hasRoadMarkingStandard, Dutch road marking standard]
-
A.
routeMarkingStandard
Indicates the standard or convention used to mark or signpost a particular route.
-
B.
hasRoadSignConvention
chosen
Indicates that there is an established standard or system governing the design, meaning, or usage of road signs in a given context.
-
C.
hasRoadStandard
Indicates that a road or roadway segment conforms to, or is governed by, a specific road design, construction, or operational standard.
-
D.
hasRoadSign
Indicates that one entity possesses, displays, or is associated with a particular road sign.
-
E.
hasRoadCharacteristics
Indicates that one entity possesses specific road-related features or attributes, such as type, condition, or structural properties.
- 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_69ef5204f7048190bf226a129858fc5b |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 27, 2026, 12:27 p.m.