Triple
T13290529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R232 |
E316548
|
entity |
| Predicate | roofOperationSpeedLimit |
P2129
|
FINISHED |
| Object | up to about 60 km/h |
—
|
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: up to about 60 km/h | Statement: [R232, roofOperationSpeedLimit, up to about 60 km/h]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roofOperationSpeedLimit Context triple: [R232, roofOperationSpeedLimit, up to about 60 km/h]
-
A.
regulatesSpeedLimitBy
Indicates that one entity determines, controls, or sets the speed limit applicable to another entity or context.
-
B.
roofOperationTime
Indicates the duration or specific time period during which a roof-related operation or mechanism is active or performed.
-
C.
hasSpeedLimit
chosen
Indicates that a specified maximum allowable speed is imposed on the associated entity or context.
-
D.
speedLimitCharacteristic
Indicates that an entity has a specific speed limit property or constraint associated with it.
-
E.
hasSpeedRestriction
Indicates that an entity is subject to a specified limit on its allowable speed.
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6535688190a5a4549b7be2d611 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:27 p.m.