Triple
T35909047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 0 series Shinkansen |
E1038553
|
entity |
| Predicate | originalServiceTopSpeed |
P106102
|
FINISHED |
| Object | 210 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: 210 km/h | Statement: [0 series Shinkansen, originalServiceTopSpeed, 210 km/h]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalServiceTopSpeed Context triple: [0 series Shinkansen, originalServiceTopSpeed, 210 km/h]
-
A.
designedServiceSpeed
chosen
Indicates the intended or specified operational speed at which a service is designed to function.
-
B.
hasTopSpeedSection
Indicates that an entity includes or is associated with a segment or portion where the maximum or top speed is defined, reached, or relevant.
-
C.
hasServiceSpeed
Indicates that an entity provides a service operating at a specified speed or performance rate.
-
D.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
E.
originalLineSpeed
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_69f76e2259608190bf6788a132e0d139 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:07 p.m.