Triple
T35221387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CR300AF |
E1016965
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Fuxing EMU |
C59279
|
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: Fuxing EMU Context triple: [CR300AF, instanceOf, Fuxing EMU]
-
A.
high-speed electric multiple unit train
chosen
A high-speed electric multiple unit train is a self-propelled, electrically powered passenger trainset composed of multiple interconnected cars, designed to operate at very high speeds with rapid acceleration, efficient braking, and streamlined aerodynamics for intercity or regional service.
-
B.
Japanese Shinkansen train series
A Japanese Shinkansen train series is a family of high-speed electric multiple unit trains designed and operated for rapid, reliable, and comfortable intercity passenger service on Japan’s dedicated bullet train 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.
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.
-
E.
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.
- 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_69f76de072908190ab65038a8a7b6a79 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:02 p.m.