Triple
T11479093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CRH380A EMU |
E272095
|
entity |
| Predicate | recordedTestSpeed |
P12248
|
FINISHED |
| Object | 486.1 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: 486.1 km/h | Statement: [CRH380A EMU, recordedTestSpeed, 486.1 km/h]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordedTestSpeed Context triple: [CRH380A EMU, recordedTestSpeed, 486.1 km/h]
-
A.
testRunSpeed
Indicates that an entity measures or evaluates the running speed performance of another entity.
-
B.
speedAchieved
chosen
Indicates that a particular speed has been reached or attained by an entity during an event or action.
-
C.
testRecord
Indicates that an entity serves as a test-specific instance or record used for validation, experimentation, or quality assurance purposes.
-
D.
soundRecordingSpeed
Indicates the recording speed at which an audio recording was captured or is intended to be played back.
-
E.
raceRecord
Indicates that there exists a recorded result or performance entry for an entity participating in a race or competitive event.
- 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_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8294f0e948190b2e106beb86e4b2c |
completed | April 9, 2026, 10:33 p.m. |
| PD | Predicate disambiguation | batch_69d8086ecd6c81908f424864857762d6 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.