Triple
T35269477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madras and Southern Mahratta Railway |
E1018625
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British colonial railway company |
C50242
|
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: British colonial railway company Context triple: [Madras and Southern Mahratta Railway, instanceOf, British colonial railway company]
-
A.
British-era railway company
chosen
A British-era railway company is an organization established during the period of British rule to build, operate, and maintain railway lines and related services, typically under colonial economic and administrative policies.
-
B.
19th-century British company
A 19th-century British company is a business organization established in Britain between 1801 and 1900, typically operating under early industrial capitalism, imperial trade networks, and evolving corporate and legal frameworks of the Victorian era.
-
C.
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.
-
D.
former British rail franchise operator
A former British rail franchise operator is a company that previously held a government-awarded contract to run passenger train services on specific routes or regions within the UK rail network.
-
E.
British colonial administrative body
A British colonial administrative body is an official governing institution established by the British Empire to manage political, economic, and legal affairs in its overseas territories.
- 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_69f76de5c4788190896ad598ae7d6bc6 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:02 p.m.