Triple
T8667930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voyager trains |
E205721
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | high-speed passenger train family |
C6337
|
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 passenger train family Context triple: [Voyager trains, instanceOf, high-speed passenger train family]
-
A.
passenger railcar family
A passenger railcar family is a group of related rail vehicles sharing a common design platform, structural features, and systems, adapted into multiple variants to serve different passenger transport roles and service requirements.
-
B.
passenger train
A passenger train is a rail vehicle or series of connected vehicles designed to transport people and their luggage between stations along a fixed route and schedule.
-
C.
diesel-electric multiple unit family
chosen
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.
-
D.
named passenger train
A named passenger train is a specific, regularly scheduled train service distinguished by a unique name and consistent route, amenities, and branding for carrying passengers.
-
E.
auto ferry train
An auto ferry train is a specialized rail service designed to transport passengers along with their vehicles—such as cars, motorcycles, and small trucks—across long distances or through otherwise impassable routes like tunnels or mountainous regions.
- 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_69ca83516ae88190aefe034b3bc589e3 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:31 p.m.