Triple
T12489289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charing Cross, Euston and Hampstead Railway |
E298519
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | London Underground precursor |
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 precursor Context triple: [Charing Cross, Euston and Hampstead Railway, instanceOf, London Underground precursor]
-
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.
Merseyrail station
A Merseyrail station is a railway facility served by the Merseyrail network, providing passenger access, ticketing, and related services on its urban and suburban routes in the Liverpool City Region.
-
C.
Inland Transport Committee
The Inland Transport Committee is a policy-making body that develops and coordinates international regulations, standards, and best practices to promote safe, efficient, and sustainable inland transport systems.
-
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.
early passenger railway
An early passenger railway is a transportation system from the 19th or early 20th century that used rail tracks and typically steam-powered locomotives to carry people between towns and cities, often marking the transition from horse-drawn carriages to mechanized mass transit.
- F. None of above. chosen
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_69d6ada377208190a36011199a4d8558 |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:56 p.m.