Triple
T28019702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gauge 1 |
E707652
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railway modelling standard |
C43923
|
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 modelling standard Context triple: [Gauge 1, instanceOf, railway modelling standard]
-
A.
railway technical standard
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.
model railway scale
chosen
A model railway scale is a standardized ratio that defines the proportional size relationship between a miniature train layout and its real-world counterpart.
-
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.
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.
-
E.
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.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 8:09 p.m.