Triple
T14737344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beijing–Tianjin Intercity Railway |
E346247
|
entity |
| Predicate | initialOperatingSpeed |
P6743
|
FINISHED |
| Object | 350 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: 350 km/h | Statement: [Beijing–Tianjin Intercity Railway, initialOperatingSpeed, 350 km/h]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialOperatingSpeed Context triple: [Beijing–Tianjin Intercity Railway, initialOperatingSpeed, 350 km/h]
-
A.
designedServiceSpeed
Indicates the intended or specified operational speed at which a service is designed to function.
-
B.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
C.
recommendedSpeed
Indicates the speed that is advised or suggested as appropriate under given conditions, rather than required or actual speed.
-
D.
currentSpeed
Indicates the present rate at which an entity is moving over time.
-
E.
originalLineSpeed
chosen
Indicates the speed at which something initially moves or operates before any changes or adjustments are made.
- 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_69d822e6f1c88190bc494d491a907114 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec73264848190be23c5f0260cbe13 |
completed | April 14, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69de8bf9331481909582045cd567d91f |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:29 a.m.