Triple
T33077066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | スカイライナー |
E846393
|
entity |
| Predicate | 最高速度 |
P2096
|
FINISHED |
| Object | 160km/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: 160km/h | Statement: [スカイライナー, 最高速度, 160km/h]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 最高速度 Context triple: [スカイライナー, 最高速度, 160km/h]
-
A.
maxSpeed
chosen
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
B.
maximumCurrentSpeed
Indicates the highest current speed value that an entity is allowed or able to reach under present conditions.
-
C.
maximumSpeedRecord
Indicates that an entity holds the highest recorded speed value (a speed record) within a given context or category.
-
D.
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.
-
E.
speedAchieved
Indicates that a particular speed has been reached or attained by an entity during an event or action.
- 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_69f3495405b88190967af2157b43b896 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:25 a.m.