Triple
T31817320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Class 350/1 |
E812170
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British Rail Class 350 subclass |
C60882
|
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 350 subclass Context triple: [British Rail Class 350/1, instanceOf, British Rail Class 350 subclass]
-
A.
subclass of British Rail Class 700
A subclass of British Rail Class 700 is a specific variant of this electric multiple unit family, distinguished by particular configurations, equipment, or service roles while sharing the core design and performance characteristics.
-
B.
British Rail Mark 3 variant
A British Rail Mark 3 variant is a specific version of the Mark 3 passenger rail coach, modified or configured for particular operational roles, comfort standards, or railway operators.
-
C.
subclass of British Rail Class 387
A subclass of British Rail Class 387 is a specific variant of these electric multiple-unit trains that shares the core 387 design but differs in configuration, equipment, or intended service use.
-
D.
British Rail Mark 3 coach sub-series
The British Rail Mark 3 coach sub-series comprises the various specialized variants of the Mark 3 passenger coach design, each adapted for different operators, services, and technical requirements within the UK rail network.
-
E.
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.
- F. None of above. chosen
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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:45 p.m.