Triple
T16533178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RegionalBahn |
E401617
|
entity |
| Predicate | typicalMaximumSpeedRange |
P2096
|
FINISHED |
| Object | up to about 160 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 about 160 km/h | Statement: [RegionalBahn, typicalMaximumSpeedRange, up to about 160 km/h]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMaximumSpeedRange Context triple: [RegionalBahn, typicalMaximumSpeedRange, up to about 160 km/h]
-
A.
maxSpeed
chosen
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
B.
hasSpeedLimitRange
Indicates that there is a specified minimum and maximum speed limit applicable to a given context or segment.
-
C.
category4UpperBound_mph
Indicates the maximum wind speed in miles per hour that defines the upper limit of Category 4 in a classification scale.
-
D.
category1UpperBound_mph
Indicates the maximum speed limit, in miles per hour, that defines the upper boundary of category 1.
-
E.
category3UpperBound_mph
Indicates the maximum wind speed in miles per hour that defines the upper limit of category 3 within a categorized scale.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32ed97b0881909de106418aca8180 |
completed | April 18, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e2969fab208190ad64164d24748c45 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:15 a.m.