Triple
T19972559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swiss locomotive classification |
E480114
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railway rolling stock classification system |
C17190
|
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: railway rolling stock classification system Context triple: [Swiss locomotive classification, instanceOf, railway rolling stock classification system]
-
A.
railroad rolling stock identifier
A railroad rolling stock identifier is a unique code or marking assigned to each rail vehicle to distinguish it from others for tracking, operations, and maintenance purposes.
-
B.
rolling stock
Rolling stock refers to all the vehicles that move on a railway, including locomotives, passenger coaches, freight wagons, and maintenance units.
-
C.
railway station classification
Railway station classification is the conceptual categorization of railway stations based on attributes such as size, passenger volume, services offered, and operational importance within a rail network.
-
D.
railway locomotive standardization scheme
chosen
A railway locomotive standardization scheme is a systematic framework for defining, organizing, and unifying the design, classification, and specifications of locomotives across a rail network to ensure compatibility, efficiency, and ease of maintenance.
-
E.
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.
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:54 p.m.