Triple
T12076460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bombardier BiLevel Coach |
E287560
|
entity |
| Predicate | typicalServiceSpeed |
P56946
|
FINISHED |
| Object | up to 160 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: up to 160 km/h | Statement: [Bombardier BiLevel Coach, typicalServiceSpeed, up to 160 km/h]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalServiceSpeed Context triple: [Bombardier BiLevel Coach, typicalServiceSpeed, up to 160 km/h]
-
A.
hasServiceSpeed
chosen
Indicates that an entity provides a service operating at a specified speed or performance rate.
-
B.
dataRate
Indicates the rate at which data is transmitted, processed, or transferred between entities over a given time interval.
-
C.
typicalSpeedup
Indicates the usual or expected performance improvement (e.g., reduction in time or increase in speed) achieved when applying one method, system, or configuration relative to another.
-
D.
recommendedSpeed
Indicates the speed that is advised or suggested as appropriate under given conditions, rather than required or actual speed.
-
E.
hasAverageSurfaceSpeed
Indicates the typical or mean speed at which something moves across a surface over a given period or distance.
- 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_69d6ab4846e081908ee7bbd66a6d3459 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902bf4f508190842927e7e0642235 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:48 p.m.