Triple
T14185856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A15 motorway (Netherlands) |
E351572
|
entity |
| Predicate | regulatesSpeed |
P43145
|
FINISHED |
| Object | motorway speed limits of the Netherlands |
—
|
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: motorway speed limits of the Netherlands | Statement: [A15 motorway (Netherlands), regulatesSpeed, motorway speed limits of the Netherlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatesSpeed Context triple: [A15 motorway (Netherlands), regulatesSpeed, motorway speed limits of the Netherlands]
-
A.
regulatesSpeedLimitBy
chosen
Indicates that one entity determines, controls, or sets the speed limit applicable to another entity or context.
-
B.
supportsSpeedControls
Indicates that an entity provides or is compatible with mechanisms to adjust or control speed.
-
C.
canReduceSpeedTo
Indicates that an entity has the capability to lower its speed to a specified level or threshold.
-
D.
hasVariableSpeedLimits
Indicates that the subject is associated with speed limits that can change depending on conditions, time, or location.
-
E.
speedAchieved
Indicates that a particular speed has been reached or attained by an entity during an event or action.
- 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_69d8278834a08190b0f1784e58d7b99c |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61cd5778819092a03597bcdcc182 |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05baed64819096590e5618a3a8ed |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:03 a.m.