Triple
T14459465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scotland Route (Network Rail) |
E358543
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railway infrastructure management division |
C13555
|
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 infrastructure management division Context triple: [Scotland Route (Network Rail), instanceOf, railway infrastructure management division]
-
A.
railway infrastructure manager
A railway infrastructure manager is an entity responsible for the planning, construction, maintenance, operation, and safe management of railway tracks, signaling systems, and related fixed installations.
-
B.
railway infrastructure element
A railway infrastructure element is any physical component of a rail system—such as tracks, signals, switches, bridges, or platforms—that supports the safe and efficient operation of trains.
-
C.
railway works section
A railway works section is a defined segment of railway infrastructure and track, managed as a unit for construction, maintenance, and operational oversight.
-
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.
railroad operating division
chosen
A railroad operating division is a geographically defined segment of a railway system managed as a unit for train operations, crew assignments, dispatching, and maintenance activities.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:19 a.m.