Triple
T33408903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H-3 |
E855517
|
entity |
| Predicate | designSpeedLimit |
P44281
|
FINISHED |
| Object | approximately 55 miles per hour |
—
|
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: approximately 55 miles per hour | Statement: [H-3, designSpeedLimit, approximately 55 miles per hour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designSpeedLimit Context triple: [H-3, designSpeedLimit, approximately 55 miles per hour]
-
A.
regulatesSpeedLimitBy
Indicates that one entity determines, controls, or sets the speed limit applicable to another entity or context.
-
B.
hasSpeedLimit
Indicates that a specified maximum allowable speed is imposed on the associated entity or context.
-
C.
speedLimitCharacteristic
chosen
Indicates that an entity has a specific speed limit property or constraint associated with it.
-
D.
previousSpeedLimit
Indicates that a specified speed limit was in effect immediately before the current or another referenced speed limit.
-
E.
designedSpeedKmH
Indicates the maximum speed in kilometers per hour that something is intended or engineered to achieve under its design specifications.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe96c2647c819082989f11e1ae3d35 |
completed | May 9, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69fe928615448190af939e5a94be55bb |
completed | May 9, 2026, 1:48 a.m. |
Created at: May 1, 2026, 1:36 a.m.