Triple
T19885989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jabalpur railway division |
E477901
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Administrative unit of Indian Railways |
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: Administrative unit of Indian Railways Context triple: [Jabalpur railway division, instanceOf, Administrative unit of Indian Railways]
-
A.
former Indian railway system
A former Indian railway system is a historically existing but now defunct or reorganized rail transport network that once operated within the geographical boundaries of India.
-
B.
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.
-
C.
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.
-
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.
rail transport company
A rail transport company is an organization that owns, operates, or manages trains and railway infrastructure to provide freight and/or passenger transportation services.
- 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_69d8e51f32b08190b3687f4f60353250 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:52 p.m.