Triple
T12801693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hikari |
E306033
|
entity |
| Predicate | relativeSpeedCategory |
P106461
|
FINISHED |
| Object | slower than Nozomi |
—
|
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: slower than Nozomi | Statement: [Hikari, relativeSpeedCategory, slower than Nozomi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeSpeedCategory Context triple: [Hikari, relativeSpeedCategory, slower than Nozomi]
-
A.
speedClass
Indicates the categorical speed level or range assigned to an entity based on how fast it moves or operates.
-
B.
relativeMotionType
Indicates the type or nature of motion occurring between two entities relative to one another.
-
C.
hasSpeedLimitCategory
Indicates that an entity is associated with a specific category or classification of speed limit.
-
D.
currentSpeed
Indicates the present rate at which an entity is moving over time.
-
E.
relativeSpeedComparedToConventionalTrains
Indicates how the speed of something compares to that of conventional trains, typically expressing whether it is faster, slower, or similar.
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e7d3f5c8190bf01bef5d263ca26 |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ed7448190b276e7fab649f7d2 |
completed | April 10, 2026, 8:56 p.m. |
| PDg | Predicate description generation | batch_69d96d88be0481908c311f1e71b61e70 |
completed | April 10, 2026, 9:37 p.m. |
Created at: April 9, 2026, 5:30 p.m.