Triple
T7599152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Revolution (Blackpool Pleasure Beach) |
E179936
|
entity |
| Predicate | hasMaxSpeed |
P2096
|
FINISHED |
| Object | approximately 45 mph |
—
|
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 45 mph | Statement: [Revolution (Blackpool Pleasure Beach), hasMaxSpeed, approximately 45 mph]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaxSpeed Context triple: [Revolution (Blackpool Pleasure Beach), hasMaxSpeed, approximately 45 mph]
-
A.
maxSpeed
chosen
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
B.
hasSpeedLimit
Indicates that a specified maximum allowable speed is imposed on the associated entity or context.
-
C.
hasVariableSpeedLimits
Indicates that the subject is associated with speed limits that can change depending on conditions, time, or location.
-
D.
hasSpeedRestriction
Indicates that an entity is subject to a specified limit on its allowable speed.
-
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_69c69f3487ec8190bf7acdf2dd91e6d6 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9d7cb288190b40ff5c9a09297d9 |
completed | March 27, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e2e42c8190afc802c4796c9cc2 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:53 p.m.