Triple
T35271152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tōkaidō Shinkansen at Shin-Osaka Station |
E1018670
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | high-speed rail station complex |
C25472
|
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: high-speed rail station complex Context triple: [Tōkaidō Shinkansen at Shin-Osaka Station, instanceOf, high-speed rail station complex]
-
A.
rapid transit station
A rapid transit station is a designated facility where passengers board, alight, and transfer between high-frequency urban rail or metro services, typically featuring platforms, ticketing areas, and access to surrounding streets or other transport modes.
-
B.
bus and rail station
A bus and rail station is a transportation hub where passengers can board, disembark, and transfer between bus and train services within an integrated facility.
-
C.
commuter rail station
A commuter rail station is a designated facility where passengers board and alight regional trains that connect suburbs or outlying areas with urban centers, typically offering platforms, ticketing, and basic passenger amenities.
-
D.
group of passenger rail terminals
A group of passenger rail terminals is a collection of interconnected or related railway stations designed for boarding, alighting, and transferring passengers within a coordinated transport network.
-
E.
passenger rail terminal
chosen
A passenger rail terminal is a dedicated facility where travelers board, disembark, and transfer between trains, supported by platforms, ticketing, waiting areas, and related passenger services.
- 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_69f76de5c4788190896ad598ae7d6bc6 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:02 p.m.