Triple
T20896188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nankai limited express EMUs |
E514542
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | electric multiple unit train type |
C24406
|
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: electric multiple unit train type Context triple: [Nankai limited express EMUs, instanceOf, electric multiple unit train type]
-
A.
diesel-electric multiple unit family
A diesel-electric multiple unit family is a group of closely related self-propelled rail vehicles that use onboard diesel engines to generate electricity for traction motors, sharing common design, components, and performance characteristics.
-
B.
electric locomotive class
An electric locomotive class is a category of railway locomotives designed and grouped by shared technical and performance characteristics, all powered by electricity from external sources such as overhead lines or third rails.
-
C.
train type
chosen
A train type is a classification that distinguishes trains based on their design, purpose, and operational characteristics, such as speed, service level, and route usage.
-
D.
rail vehicle
A rail vehicle is a wheeled conveyance designed to operate on railway tracks for transporting passengers, freight, or performing specialized rail-related tasks.
-
E.
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.
- 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_69e0b4f7ebe48190952a85547a0f31a1 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:47 p.m.