Triple
T14237650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hokkaido Shinkansen |
E352926
|
entity |
| Predicate | plannedExtensionOpening |
P61280
|
FINISHED |
| Object | around 2030s |
—
|
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: around 2030s | Statement: [Hokkaido Shinkansen, plannedExtensionOpening, around 2030s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedExtensionOpening Context triple: [Hokkaido Shinkansen, plannedExtensionOpening, around 2030s]
-
A.
plannedExtensionTo
Indicates that one entity is intended or scheduled to be extended, expanded, or continued by another entity in the future.
-
B.
extensionOpening
Indicates that one entity serves as an opening or access point that leads into or connects to an extension of another entity.
-
C.
extensionOpeningPeriod
chosen
Indicates the time span during which an extension (such as a facility, service, or feature) is open or available for use.
-
D.
plannedExtensionDirection
Indicates the intended directional path or orientation along which something is planned to be extended in the future.
-
E.
extensionOpened
Indicates that a software extension has been activated or launched from its previously closed or inactive state.
- 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_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. |
Created at: April 10, 2026, 1:07 a.m.