Triple
T16071654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paris–Zurich high-speed service |
E389876
|
entity |
| Predicate | maximumSpeedApproximate |
P2096
|
FINISHED |
| Object | up to 320 km/h on high-speed sections |
—
|
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 320 km/h on high-speed sections | Statement: [Paris–Zurich high-speed service, maximumSpeedApproximate, up to 320 km/h on high-speed sections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumSpeedApproximate Context triple: [Paris–Zurich high-speed service, maximumSpeedApproximate, up to 320 km/h on high-speed sections]
-
A.
maxSpeed
chosen
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
B.
speedAchieved
Indicates that a particular speed has been reached or attained by an entity during an event or action.
-
C.
maximumRPM
Indicates the highest rotational speed, in revolutions per minute, that an entity is designed or allowed to operate at.
-
D.
category1UpperBound_mph
Indicates the maximum speed limit, in miles per hour, that defines the upper boundary of category 1.
-
E.
hasSpeedLimitCharacteristic
Indicates that an entity is associated with a specific speed limit property or constraint.
- 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_69d86daf32ec8190a8c0466c8f49c3c0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1827ad7c88190b867da511cbfb7fa |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:57 a.m.