Triple
T20026565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HSL-Zuid railway bridge |
E494997
|
entity |
| Predicate | designedForSpeedUpTo |
P138039
|
FINISHED |
| Object | 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: 300 km/h | Statement: [HSL-Zuid railway bridge, designedForSpeedUpTo, 300 km/h]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForSpeedUpTo Context triple: [HSL-Zuid railway bridge, designedForSpeedUpTo, 300 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.
designedServiceSpeed
Indicates the intended or specified operational speed at which a service is designed to function.
-
C.
marketedSpeedName
Indicates the branded or advertised name used to describe the speed of a product or service.
-
D.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
E.
speedupType
Indicates the kind or category of performance improvement achieved relative to a baseline.
- 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6628e1eec81908e4c9b2b0b68f0e4 |
completed | April 20, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69e54ce752748190a0a1ffddd0372271 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:35 p.m.