Triple
T24668255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SRT |
E610745
|
entity |
| Predicate | approximateOperatingSpeed |
P157671
|
FINISHED |
| Object | up to 300 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 300 km/h | Statement: [SRT, approximateOperatingSpeed, up to 300 km/h]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateOperatingSpeed Context triple: [SRT, approximateOperatingSpeed, up to 300 km/h]
-
A.
operatingFrequencyApproximate
Indicates an approximate or estimated operating frequency at which an entity functions or is designed to function.
-
B.
hasAverageSurfaceSpeed
Indicates the typical or mean speed at which something moves across a surface over a given period or distance.
-
C.
currentSpeed
Indicates the present rate at which an entity is moving over time.
-
D.
baseSpeed
Indicates the default or starting rate at which an entity moves or operates before any modifications or adjustments.
-
E.
plannedSpeed
Indicates the intended or target speed that an entity is expected or scheduled to maintain, rather than its actual current speed.
- F. None of above. chosen
Provenance (4 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_69e2c4d505cc8190981881df06c0bf52 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
| PDg | Predicate description generation | batch_69f44a3adb7c8190941572f718b3b93c |
completed | May 1, 2026, 6:37 a.m. |
Created at: April 18, 2026, 2:41 a.m.