Triple
T35318879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chūō Shinkansen |
E1019981
|
entity |
| Predicate | plannedTestSpeedRecord |
P125449
|
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: [Chūō Shinkansen, plannedTestSpeedRecord, 603 km/h]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedTestSpeedRecord Context triple: [Chūō Shinkansen, plannedTestSpeedRecord, 603 km/h]
-
A.
testSpeedRecordDate
Indicates the date on which a speed test or speed record measurement was performed or officially recorded.
-
B.
plannedSpeed
chosen
Indicates the intended or target speed that an entity is expected or scheduled to maintain, rather than its actual current speed.
-
C.
plannedNumberOfTests
Indicates the total count of tests that are intended or scheduled to be conducted for a given context or period.
-
D.
previousRecordSpeed
Indicates that one record speed precedes another in time, representing the earlier benchmark before a new speed is achieved.
-
E.
testRunSpeed
Indicates that an entity measures or evaluates the running speed performance of another entity.
- 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: May 3, 2026, 4:03 p.m.