Triple
T30753730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fehmarnbelt Tunnel |
E783022
|
entity |
| Predicate | railDesignSpeedKmPerHour |
P138039
|
FINISHED |
| Object | 200 |
—
|
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: 200 | Statement: [Fehmarnbelt Tunnel, railDesignSpeedKmPerHour, 200]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railDesignSpeedKmPerHour Context triple: [Fehmarnbelt Tunnel, railDesignSpeedKmPerHour, 200]
-
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.
speedAtDerailmentApprox
Indicates the approximate speed an entity was traveling at the moment it derailed.
-
D.
governingSpeedRange
Indicates the range of speeds within which a governing or limiting mechanism is intended to operate or apply.
-
E.
speedLimitCharacteristic
Indicates that an entity has a specific speed limit property or constraint associated with it.
- 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_69f224af8d8481908bea03890c5618be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:39 p.m.