Triple
T12953309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Northern, Piccadilly and Brompton Railway |
E309946
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | London Underground railway company |
C31538
|
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: London Underground railway company Context triple: [Great Northern, Piccadilly and Brompton Railway, instanceOf, London Underground railway company]
-
A.
London Underground depot
A London Underground depot is a specialized facility where Underground trains are stored, maintained, cleaned, and prepared for daily service on the network.
-
B.
London Underground precursor
chosen
A London Underground precursor is any early urban rail or transport system, proposal, or technological development that directly influenced or led to the creation of the London Underground.
-
C.
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.
-
D.
street railway company
A street railway company is a business entity that owns, operates, and maintains streetcars or trams running on fixed rails along public streets to provide urban passenger transportation.
-
E.
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.
- 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_69d7bdfb57a88190836b743e2825feca |
completed | April 9, 2026, 2:55 p.m. |
Created at: April 9, 2026, 5:44 p.m.