Triple
T37221316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shin-Osaka – Hakata |
E922889
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Shinkansen corridor segment |
C61166
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Shinkansen corridor segment Context triple: [Shin-Osaka – Hakata, instanceOf, Shinkansen corridor segment]
-
A.
suburban railway corridor
A suburban railway corridor is a dedicated rail route connecting city centers with surrounding residential suburbs, designed to support frequent, high-capacity commuter train services.
-
B.
transport corridor segment
chosen
A transport corridor segment is a defined linear portion of a transportation route (such as a road, rail line, or shipping lane) characterized by consistent physical, operational, and regulatory attributes used for planning, management, and analysis.
-
C.
rapid transit line segment
A rapid transit line segment is a contiguous portion of a rapid transit route between two defined points (such as stations, junctions, or terminals) that carries high-frequency, high-capacity passenger rail service.
-
D.
mini-shinkansen line
A mini-shinkansen line is a converted narrow-gauge railway upgraded to standard gauge and high-speed standards, allowing Shinkansen trains to run directly onto conventional lines while maintaining through-service with the main high-speed network.
-
E.
railway line
A railway line is a fixed transportation route consisting of tracks, signaling, and related infrastructure along which trains operate between defined locations.
- F. None of above.
Provenance (1 batch)
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_69f76ea6f5288190b8d9988f613811c0 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:15 p.m.