Triple
T19972514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UIC classification |
E480113
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railway standard |
C17465
|
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 standard Context triple: [UIC classification, instanceOf, railway standard]
-
A.
railway technical standard
chosen
A railway technical standard is a formalized set of specifications and requirements that define the design, construction, operation, and maintenance criteria for railway systems to ensure safety, interoperability, and performance.
-
B.
United States railroad standard
United States railroad standard: A conceptual class representing the set of technical, operational, and safety specifications that govern the design, construction, and operation of railroads within the United States.
-
C.
railway locomotive standardization scheme
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.
-
D.
public railway
A public railway is a government- or publicly-owned rail transport system that provides scheduled passenger and/or freight services accessible to the general population, typically operating on standardized tracks and infrastructure.
-
E.
standardized rail interface
A standardized rail interface is a uniform physical and electrical connection system that allows different rail vehicles, components, or infrastructure elements to interoperate safely and efficiently across multiple networks or manufacturers.
- 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.