Triple
T23590863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokyo Metro Hanzomon Line rolling stock |
E582472
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | electric multiple unit type collection |
C14922
|
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: electric multiple unit type collection Context triple: [Tokyo Metro Hanzomon Line rolling stock, instanceOf, electric multiple unit type collection]
-
A.
diesel-electric multiple unit family
A diesel-electric multiple unit family is a group of closely related self-propelled rail vehicles that use onboard diesel engines to generate electricity for traction motors, sharing common design, components, and performance characteristics.
-
B.
electric locomotive class
An electric locomotive class is a category of railway locomotives designed and grouped by shared technical and performance characteristics, all powered by electricity from external sources such as overhead lines or third rails.
-
C.
passenger railcar fleet
chosen
A passenger railcar fleet is a managed collection of rail vehicles designed and maintained to transport people safely and efficiently across a rail network.
-
D.
rail vehicle
A rail vehicle is a wheeled conveyance designed to operate on railway tracks for transporting passengers, freight, or performing specialized rail-related tasks.
-
E.
bi-mode multiple unit train
A bi-mode multiple unit train is a self-propelled trainset capable of operating using both external electric power (from overhead lines or third rail) and onboard diesel or battery power, allowing seamless running across electrified and non-electrified routes.
- 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_69e248f9e0a08190814772847003b1ff |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:42 p.m.