Triple
T17895069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow–Saint Petersburg railway corridor |
E447411
|
entity |
| Predicate | maxServiceSpeedKmPerH |
P106102
|
FINISHED |
| Object | 250 |
—
|
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: 250 | Statement: [Moscow–Saint Petersburg railway corridor, maxServiceSpeedKmPerH, 250]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxServiceSpeedKmPerH Context triple: [Moscow–Saint Petersburg railway corridor, maxServiceSpeedKmPerH, 250]
-
A.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
B.
designedServiceSpeed
chosen
Indicates the intended or specified operational speed at which a service is designed to function.
-
C.
speedLimitCharacteristic
Indicates that an entity has a specific speed limit property or constraint associated with it.
-
D.
hasTopSpeedSection
Indicates that an entity includes or is associated with a segment or portion where the maximum or top speed is defined, reached, or relevant.
-
E.
maximumWaterSpeed_kmh
Indicates the highest speed, measured in kilometers per hour, at which an entity can move through water.
- 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_69d8b9f59bd48190a6fc925a855b8bac |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49d7eb4f48190951e26975b57873b |
completed | April 19, 2026, 9:16 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e9b77c8190bbfb508f28dfacfa |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:19 a.m.