Triple
T20745034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jhansi railway division |
E510557
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Railway division of India |
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 division of India Context triple: [Jhansi railway division, instanceOf, Railway division of India]
-
A.
zone of Indian Railways
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.
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.
-
C.
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.
-
D.
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.
-
E.
princely state railway
A princely state railway is a railway system owned, financed, or operated by a semi-autonomous princely state under indirect colonial or imperial oversight, typically integrated to varying degrees with a larger national or imperial rail network.
- 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_69e0b4c845e88190b4c5f3ae79291182 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:33 p.m.