Triple
T34771611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L0 Series maglev trainsets |
E1002376
|
entity |
| Predicate | testSpeedRecordDate |
P181827
|
FINISHED |
| Object | 2015-04-21 |
—
|
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: 2015-04-21 | Statement: [L0 Series maglev trainsets, testSpeedRecordDate, 2015-04-21]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testSpeedRecordDate Context triple: [L0 Series maglev trainsets, testSpeedRecordDate, 2015-04-21]
-
A.
previousRecordSpeed
Indicates that one record speed precedes another in time, representing the earlier benchmark before a new speed is achieved.
-
B.
topSpeedRecordYear
Indicates the year in which an entity achieved its highest recorded top speed.
-
C.
windSpeedRecordDate
Indicates the date on which a particular wind speed measurement or record was observed or recorded.
-
D.
maximumSpeedRecord
Indicates that an entity holds the highest recorded speed value (a speed record) within a given context or category.
-
E.
peacetimeSpeedRecord
Indicates the maximum speed achieved under non-combat, peacetime conditions, recognized as a record.
- 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_69f76db20dac8190b1e8d0ca4dc1d59f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7824dc3f0819092a5102895b4a478 |
completed | May 3, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f7817c79e081908e685c48165e086b |
completed | May 3, 2026, 5:10 p.m. |
Created at: May 3, 2026, 3:59 p.m.