Triple
T35292168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CR300BF |
E1019256
|
entity |
| Predicate | designedMaximumOperatingSpeed |
P138039
|
FINISHED |
| Object | 250 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: 250 km/h | Statement: [CR300BF, designedMaximumOperatingSpeed, 250 km/h]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedMaximumOperatingSpeed Context triple: [CR300BF, designedMaximumOperatingSpeed, 250 km/h]
-
A.
designedSpeedKmH
chosen
Indicates the maximum speed in kilometers per hour that something is intended or engineered to achieve under its design specifications.
-
B.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
C.
designedServiceSpeed
Indicates the intended or specified operational speed at which a service is designed to function.
-
D.
governingSpeedRange
Indicates the range of speeds within which a governing or limiting mechanism is intended to operate or apply.
-
E.
speedAtDerailmentApprox
Indicates the approximate speed an entity was traveling at the moment it derailed.
- 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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff109695008190a22b47ef8be2e3f9 |
completed | May 9, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69ff0f243ea88190970d2c520b55c816 |
completed | May 9, 2026, 10:40 a.m. |
Created at: May 3, 2026, 4:03 p.m.