Triple
T2868526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokaido Shinkansen |
E63499
|
entity |
| Predicate | designedSpeedClass_kmh |
P9902
|
FINISHED |
| Object | up to 300 |
—
|
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: up to 300 | Statement: [Tokaido Shinkansen, designedSpeedClass_kmh, up to 300]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedSpeedClass_kmh Context triple: [Tokaido Shinkansen, designedSpeedClass_kmh, up to 300]
-
A.
speedClass
chosen
Indicates the categorical speed level or range assigned to an entity based on how fast it moves or operates.
-
B.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
C.
transportCharacteristic
Indicates a relationship where a specific characteristic, property, or feature is attributed to a mode or instance of transport.
-
D.
category4UpperBound_mph
Indicates the maximum wind speed in miles per hour that defines the upper limit of Category 4 in a classification scale.
-
E.
category3UpperBound_mph
Indicates the maximum wind speed in miles per hour that defines the upper limit of category 3 within a categorized scale.
- 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_69ab4c42fb8c8190b36e161d47c03b81 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdfdfef1881909dc52a1b34cd24e3 |
completed | March 7, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69abdd123ec48190af50a1859aea50b7 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.