Triple
T34771610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L0 Series maglev trainsets |
E1002376
|
entity |
| Predicate | testSpeedRecord |
P58444
|
FINISHED |
| Object | 603 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: 603 km/h | Statement: [L0 Series maglev trainsets, testSpeedRecord, 603 km/h]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testSpeedRecord Context triple: [L0 Series maglev trainsets, testSpeedRecord, 603 km/h]
-
A.
testRunSpeed
Indicates that an entity measures or evaluates the running speed performance of another entity.
-
B.
previousRecordSpeed
Indicates that one record speed precedes another in time, representing the earlier benchmark before a new speed is achieved.
-
C.
maximumSpeedRecord
chosen
Indicates that an entity holds the highest recorded speed value (a speed record) within a given context or category.
-
D.
speedMeasurementMethod
Indicates the method or technique used to measure the speed of an entity or process.
-
E.
peacetimeSpeedRecord
Indicates the maximum speed achieved under non-combat, peacetime conditions, recognized as a record.
- 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_69f76db20dac8190b1e8d0ca4dc1d59f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.