Triple
T24433250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Class 165/1 |
E616053
|
entity |
| Predicate | topSpeedKilometresPerHour |
P138039
|
FINISHED |
| Object | 120 |
—
|
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: 120 | Statement: [British Rail Class 165/1, topSpeedKilometresPerHour, 120]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topSpeedKilometresPerHour Context triple: [British Rail Class 165/1, topSpeedKilometresPerHour, 120]
-
A.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
B.
designedSpeedKmH
chosen
Indicates the maximum speed in kilometers per hour that something is intended or engineered to achieve under its design specifications.
-
C.
acceleration0To100Kmh
Indicates the rate or time it takes for something to accelerate from 0 to 100 kilometers per hour.
-
D.
hasTopSpeedSection
Indicates that an entity includes or is associated with a segment or portion where the maximum or top speed is defined, reached, or relevant.
-
E.
maximumSpeedRecord
Indicates that an entity holds the highest recorded speed value (a speed record) within a given context or category.
- 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_69e2d7ec44b081909ccaf1f3bbec0641 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2978469a081909f17b6955809bbef |
completed | April 29, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:16 a.m.