Triple
T32537684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London King’s Cross – Edinburgh Waverley |
E831631
|
entity |
| Predicate | maximumPermittedSpeed |
P2129
|
FINISHED |
| Object | 125 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: 125 mph | Statement: [London King’s Cross – Edinburgh Waverley, maximumPermittedSpeed, 125 mph]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumPermittedSpeed Context triple: [London King’s Cross – Edinburgh Waverley, maximumPermittedSpeed, 125 mph]
-
A.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
B.
governingSpeedRange
Indicates the range of speeds within which a governing or limiting mechanism is intended to operate or apply.
-
C.
speedLimitCharacteristic
Indicates that an entity has a specific speed limit property or constraint associated with it.
-
D.
hasSpeedLimit
chosen
Indicates that a specified maximum allowable speed is imposed on the associated entity or context.
-
E.
maximumBusSpeed
Indicates the highest speed that a bus is allowed or able to travel under specified conditions.
- 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_69f34924b1cc8190ad3aca0c0f012a7e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 1, 2026, 1:01 a.m.