Triple
T14739351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Western Railway zone |
E346300
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | railway zone of India |
C29559
|
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 zone of India Context triple: [South Western Railway zone, instanceOf, railway zone of India]
-
A.
zone of Indian Railways
chosen
A zone of Indian Railways is a major administrative and operational division that oversees railway infrastructure, train operations, and services within a defined geographic region of India’s rail network.
-
B.
Indian Railways recruitment examination
The Indian Railways recruitment examination is a competitive, nationwide test conducted by Indian Railways and the Railway Recruitment Boards to select eligible candidates for various technical, non-technical, and security-related posts across the railway network.
-
C.
commuter rail zone
A commuter rail zone is a designated geographic area used to determine fares, ticketing, and service boundaries for regional passenger rail travel.
-
D.
region of British Railways
A region of British Railways is a large administrative and operational division of the national rail network, responsible for managing railway services, infrastructure, and staff within a defined geographic area of Great Britain.
-
E.
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.
- 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_69d822e6f1c88190bc494d491a907114 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:29 a.m.