Triple
T5502127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Modernisation Plan of the 1950s |
E144352
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railway modernisation programme |
C17897
|
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 modernisation programme Context triple: [Modernisation Plan of the 1950s, instanceOf, railway modernisation programme]
-
A.
railway modernisation project
chosen
A railway modernisation project is an initiative that upgrades existing rail infrastructure, technology, and operations to improve capacity, safety, efficiency, and passenger experience.
-
B.
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.
-
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.
railway network
A railway network is an interconnected system of tracks, stations, signaling, and rolling stock that enables the organized movement of trains between multiple locations.
-
E.
railway engineering complex
A railway engineering complex is an integrated facility where railway infrastructure, rolling stock, and related systems are designed, constructed, tested, maintained, and managed.
- 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_69c008f5a2748190bce7a39aabf87a6d |
completed | March 22, 2026, 3:21 p.m. |
Created at: March 22, 2026, 3:32 p.m.