Triple
T34621196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail Class 37/0 |
E889006
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British Rail Class 37 variant |
C61621
|
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 37 variant Context triple: [British Rail Class 37/0, instanceOf, British Rail Class 37 variant]
-
A.
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.
-
B.
British Rail Mark 2 coach variant
A British Rail Mark 2 coach variant is a specific design iteration within the Mark 2 family of passenger railway carriages, distinguished by particular structural, interior, and technical features tailored to different service requirements and eras.
-
C.
British Rail Class 350 subclass
The British Rail Class 350 subclass is a specific variant within the Class 350 family of electric multiple units, distinguished by particular technical specifications, interior layouts, and operational roles on the UK rail network.
-
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.
British Rail EMU
A British Rail EMU is an electric multiple unit train operated on the British railway network, consisting of self-propelled carriages powered by electricity from overhead lines or third-rail systems for passenger service.
- 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_69f349d584e08190b40b9f6281ad50c4 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:04 a.m.