Triple
T24479933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shinkansen lines |
E617343
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | high-speed railway network |
C3549
|
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 railway network Context triple: [Shinkansen lines, instanceOf, high-speed railway network]
-
A.
railway network
chosen
A railway network is an interconnected system of tracks, stations, signaling, and rolling stock that enables the organized movement of trains between multiple locations.
-
B.
rapid rail system
A rapid rail system is a high-speed, high-capacity railway network designed to transport large numbers of passengers quickly and efficiently between urban or regional destinations using dedicated tracks and frequent service.
-
C.
rapid transit network
A rapid transit network is an integrated system of high-capacity, high-frequency urban rail or bus lines designed to move large numbers of passengers quickly and efficiently across a metropolitan area.
-
D.
high-speed test train
A high-speed test train is a specialized railway vehicle designed to operate at very high velocities to evaluate, validate, and optimize track infrastructure, signaling systems, and rolling stock performance under extreme operating conditions.
-
E.
proposed high-speed ground transportation system
A proposed high-speed ground transportation system is a conceptual network of advanced vehicles, infrastructure, and control technologies designed to move passengers or freight rapidly and efficiently between destinations along dedicated terrestrial corridors.
- 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_69e2d7f3ae788190b683394db15f220e |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:21 a.m.