Triple
T38429461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoovers |
E903758
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British Rail Class 50 locomotive |
C66052
|
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 50 locomotive Context triple: [Hoovers, instanceOf, British Rail Class 50 locomotive]
-
A.
British Rail Class 37 variant
A British Rail Class 37 variant is a specific sub-type of the Class 37 diesel-electric locomotive distinguished by modifications in equipment, performance, or configuration for particular operational roles or eras.
-
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.
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 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.
-
E.
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.
- 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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:31 p.m.