Triple
T20088611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shay locomotive |
E496204
|
entity |
| Predicate | hasTypicalSpeedRange |
P37470
|
FINISHED |
| Object | low speed |
—
|
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: low speed | Statement: [Shay locomotive, hasTypicalSpeedRange, low speed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalSpeedRange Context triple: [Shay locomotive, hasTypicalSpeedRange, low speed]
-
A.
hasTypicalVelocity
chosen
Indicates that an entity is associated with a characteristic or commonly observed speed at which it typically moves or operates.
-
B.
hasSlewRateTypical
Indicates that an entity is characterized by a specified typical (nominal) slew rate value.
-
C.
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.
-
D.
designedSpeedKmH
Indicates the maximum speed in kilometers per hour that something is intended or engineered to achieve under its design specifications.
-
E.
hasSpeedLimitRange
Indicates that there is a specified minimum and maximum speed limit applicable to a given context or segment.
- 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_69da626eee3881909f3454986d4a6511 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6655d65a88190a510132f36341b6c |
completed | April 20, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_69e54cf369b88190931532420517dac7 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:17 p.m.