Triple
T21132655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adelante |
E520726
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British Rail Class 180 train |
C21330
|
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: British Rail Class 180 train Context triple: [Adelante, instanceOf, British Rail Class 180 train]
-
A.
British Rail second-generation DMU
chosen
A British Rail second-generation DMU is a diesel multiple unit train introduced from the 1980s onward, featuring improved performance, comfort, and safety over first-generation units and designed for regional and suburban passenger services across the UK rail network.
-
B.
InterCityExpress variant
An InterCityExpress variant is a specific model or configuration of high-speed ICE train designed for particular routes, capacities, or service requirements within an intercity rail network.
-
C.
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.
-
D.
TGV Réseau
TGV Réseau is a class of high-speed electric multiple unit trains operated by SNCF in France, designed for long-distance services on the French high-speed rail network.
-
E.
Electrostar family
The Electrostar family is a series of modern electric multiple-unit passenger trains designed for suburban and regional services, known for their modular construction and widespread use in the UK rail network.
- 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_69e0b50b53048190ae34e8abbe3c5ada |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 2:56 p.m.