Triple
T8623610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ED4M electric multiple unit |
E204229
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | suburban electric train |
C12293
|
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: suburban electric train Context triple: [ED4M electric multiple unit, instanceOf, suburban electric train]
-
A.
suburban commuter train
chosen
A suburban commuter train is a passenger rail service designed to transport people efficiently between residential suburbs and urban centers, typically operating on fixed schedules with frequent stops during peak travel times.
-
B.
commuter rail line
A commuter rail line is a passenger train service that operates on fixed tracks and schedules to connect suburban or outlying areas with a central city, primarily serving daily work and school commuters.
-
C.
elevated railway
An elevated railway is a rail transport system in which tracks and stations are built on raised structures above ground level, typically supported by columns or girders, to avoid interference with street traffic.
-
D.
metro train
A metro train is an electrically powered, multi-car rail vehicle designed to transport large numbers of passengers quickly and frequently along dedicated urban and suburban transit lines.
-
E.
interurban railroad
An interurban railroad is an electric railway system that provides passenger and sometimes freight service between cities and towns, typically operating on dedicated tracks or street-running routes over medium distances.
- 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_69ca834a4ea0819094970dceb9e389f3 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:26 p.m.