Triple
T37248450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shin-Aomori–Shin-Hakodate-Hokuto |
E923925
|
entity |
| Predicate | openedForShinkansenService |
P141239
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [Shin-Aomori–Shin-Hakodate-Hokuto, openedForShinkansenService, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedForShinkansenService Context triple: [Shin-Aomori–Shin-Hakodate-Hokuto, openedForShinkansenService, 2016]
-
A.
ShinkansenServiceStarted
chosen
Indicates that a Shinkansen (high-speed rail) service has commenced operation on a particular route or section.
-
B.
openedForCommuterService
Indicates that a transportation facility or route began operating specifically to serve regular commuter traffic.
-
C.
hasShinkansenStop
Indicates that a location is served by and includes a stop for a Shinkansen (high-speed rail) line.
-
D.
openedForTransilienService
Indicates that a facility or location was officially opened to provide Transilien rail service.
-
E.
operatesShinkansenSection
Indicates that an entity operates or manages the service of a specific section of a Shinkansen (high-speed rail) line.
- 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_69f76eaabb4c819093b751b139dad551 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
Created at: May 3, 2026, 4:15 p.m.