Triple
T5493701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Class 158 |
E123762
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Express Sprinter 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: Express Sprinter family Context triple: [British Rail Class 158, instanceOf, Express Sprinter 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.
APU family
APU family is a group of closely related auxiliary power units that share common design characteristics, components, and operational behaviors within an aircraft or vehicle power system.
-
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.
Turbostar family
The Turbostar family is a series of regional diesel multiple unit trains designed for short- to medium-distance passenger services, known for their modular construction and widespread use in the UK rail network.
-
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_69bd464a2d908190869324ce176779c8 |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2:10 p.m.