Triple
T12666678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fuxing series EMU |
E302568
|
entity |
| Predicate | designedServiceSpeed |
P106102
|
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: [Fuxing series EMU, designedServiceSpeed, 350 km/h]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedServiceSpeed Context triple: [Fuxing series EMU, designedServiceSpeed, 350 km/h]
-
A.
hasServiceSpeed
Indicates that an entity provides a service operating at a specified speed or performance rate.
-
B.
marketedSpeedName
Indicates the branded or advertised name used to describe the speed of a product or service.
-
C.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
D.
recommendedSpeed
Indicates the speed that is advised or suggested as appropriate under given conditions, rather than required or actual speed.
-
E.
speedAchieved
Indicates that a particular speed has been reached or attained by an entity during an event or action.
- F. None of above. chosen
Provenance (4 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_69d7bded71a88190bb76e2413af9ea66 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96181c40481908f3e2717f5472b85 |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b78ce8819091f15dd5013e6da5 |
completed | April 10, 2026, 8:42 p.m. |
| PDg | Predicate description generation | batch_69d96179c7648190a05a13991d62bebb |
completed | April 10, 2026, 8:45 p.m. |
Created at: April 9, 2026, 5:19 p.m.