Triple
T21436724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Region (historical) |
E528832
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former railway administrative division |
C17999
|
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: former railway administrative division Context triple: [Southern Region (historical), instanceOf, former railway administrative division]
-
A.
former railway facility
A former railway facility is a decommissioned or repurposed site that once served operational functions for rail transport, such as stations, depots, yards, or maintenance buildings.
-
B.
former railway station
A former railway station is a decommissioned train facility that once served passengers or freight but is no longer in active railway use.
-
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.
region of British Railways
chosen
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.
former administrative territorial entity
A former administrative territorial entity is a geographic area that once functioned as an official unit of government or administration but has since been dissolved, merged, or reorganized and no longer holds that status.
- 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_69e0c4569fa081908101baa24f8745db |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:03 p.m.