Triple
T19972441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UIC wheel arrangement classification |
E480111
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railway classification system |
C42503
|
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 classification system Context triple: [UIC wheel arrangement classification, instanceOf, railway classification system]
-
A.
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.
-
B.
railway location coding system
A railway location coding system is a standardized scheme for assigning unique codes to specific points, facilities, and segments along a rail network to support identification, operations, and data management.
-
C.
railroad classification yard
A railroad classification yard is a specialized rail facility where freight cars are sorted, assembled, and dispatched into new trains based on their destinations.
-
D.
railway signaling system
A railway signaling system is an integrated set of trackside and onboard equipment, rules, and communication protocols that control train movements to ensure safe separation, efficient routing, and protection against collisions.
-
E.
fare classification system
A fare classification system is a structured framework that categorizes transportation or ticket prices into distinct classes based on rules, restrictions, and customer or service attributes to manage pricing, availability, and revenue.
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:54 p.m.