Triple
T18366663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glasgow North Electric scheme |
E440064
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railway modernization scheme |
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 modernization scheme Context triple: [Glasgow North Electric scheme, instanceOf, railway modernization scheme]
-
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.
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.
-
C.
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.
-
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 policy implementation
Railway policy implementation is the process of translating rail-related laws, regulations, and strategic plans into concrete operational actions, projects, and standards across the railway system.
- 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_69d8b918221c8190a9f7b563d64ac677 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:38 a.m.