Triple
T14237648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hokkaido Shinkansen |
E352926
|
entity |
| Predicate | futureTerminusStation |
P113337
|
FINISHED |
| Object | Sapporo Station |
—
|
NE NERFINISHED |
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: Sapporo Station | Statement: [Hokkaido Shinkansen, futureTerminusStation, Sapporo Station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: futureTerminusStation Context triple: [Hokkaido Shinkansen, futureTerminusStation, Sapporo Station]
-
A.
terminusStation
Indicates that a station serves as the final endpoint or terminal stop for a given route or service.
-
B.
railwayUpperTerminus
Indicates that a railway line or route reaches its upper (typically higher-altitude or upstream) terminal endpoint at the related location.
-
C.
nextStationEast
Indicates that one station is the immediate next station to the east of another station along a route or line.
-
D.
nearbyTerminus
Indicates that one terminus (end point or final stop) is located close to another terminus in space.
-
E.
railroadTerminusFor
Indicates that one location serves as the end point or final station of a particular railroad line for another location.
- 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de62422e28819089e7115052a28c96 |
completed | April 14, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69de05bf069c8190b69f00f00f5eb126 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239a02e881909b0e2679487e4ab2 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 10, 2026, 1:07 a.m.