Triple
T22013897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanshin Expressway Company Limited |
E543651
|
entity |
| Predicate | hasMainRouteNetwork |
P55123
|
FINISHED |
| Object | Hanshin Expressway Route 31 Kobe-Yamate Route |
—
|
NE NERFINISHED |
How this triple was built (3 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: Hanshin Expressway Route 31 Kobe-Yamate Route | Statement: [Hanshin Expressway Company Limited, hasMainRouteNetwork, Hanshin Expressway Route 31 Kobe-Yamate Route]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hanshin Expressway Route 31 Kobe-Yamate Route Context triple: [Hanshin Expressway Company Limited, hasMainRouteNetwork, Hanshin Expressway Route 31 Kobe-Yamate Route]
-
A.
Hanshin Expressway
The Hanshin Expressway is a major urban expressway network serving the Osaka–Kobe–Kyoto region of Japan, known for its elevated routes and heavy commuter and freight traffic.
-
B.
Nishinomiya Expressway
Nishinomiya Expressway is a regional expressway in Japan that serves the Nishinomiya area, connecting local interchanges to the broader highway network.
-
C.
Kobe-Awaji-Naruto Expressway
The Kobe-Awaji-Naruto Expressway is a major Japanese highway linking the city of Kobe on Honshu with Awaji Island and Tokushima Prefecture on Shikoku via a series of long-span bridges, including the Akashi Kaikyō Bridge.
-
D.
Kinki Expressway
The Kinki Expressway is a major Japanese expressway serving the Kansai (Kinki) region, facilitating high-speed road travel and regional connectivity around cities such as Osaka and Kyoto.
-
E.
Higashi-Osaka Route
The Higashi-Osaka Route is a major urban expressway in the Osaka area of Japan that facilitates east–west traffic through the city of Higashiōsaka and its surroundings.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Hanshin Expressway Route 31 Kobe-Yamate Route Target entity description: Hanshin Expressway Route 31 Kobe-Yamate Route is an urban expressway in Kobe, Japan, forming part of the Hanshin Expressway network that connects central Kobe with surrounding areas.
-
A.
Hanshin Expressway
chosen
The Hanshin Expressway is a major urban expressway network serving the Osaka–Kobe–Kyoto region of Japan, known for its elevated routes and heavy commuter and freight traffic.
-
B.
Nishinomiya Expressway
Nishinomiya Expressway is a regional expressway in Japan that serves the Nishinomiya area, connecting local interchanges to the broader highway network.
-
C.
Kobe-Awaji-Naruto Expressway
The Kobe-Awaji-Naruto Expressway is a major Japanese highway linking the city of Kobe on Honshu with Awaji Island and Tokushima Prefecture on Shikoku via a series of long-span bridges, including the Akashi Kaikyō Bridge.
-
D.
Kinki Expressway
The Kinki Expressway is a major Japanese expressway serving the Kansai (Kinki) region, facilitating high-speed road travel and regional connectivity around cities such as Osaka and Kyoto.
-
E.
Higashi-Osaka Route
The Higashi-Osaka Route is a major urban expressway in the Osaka area of Japan that facilitates east–west traffic through the city of Higashiōsaka and its surroundings.
- F. None of above.
Provenance (2 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_69e11e2db934819095556760c7d85e4d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127a6bf6081909865781ea7937a1b |
completed | April 28, 2026, 9:33 p.m. |
Created at: April 16, 2026, 8:22 p.m.