Triple
T4697812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bank and Monument stations |
E104192
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | London Underground station complex |
C7253
|
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 station complex Context triple: [Bank and Monument stations, instanceOf, London Underground station complex]
-
A.
Department for Transport station category
A Department for Transport station category is a classification assigned by the UK Department for Transport that groups railway stations into standardized categories based on factors such as passenger usage, facilities, and strategic importance.
-
B.
public transit station
chosen
A public transit station is a designated facility where passengers can access, board, transfer between, and disembark from public transportation services such as buses, trains, or subways.
-
C.
Berlin U-Bahn station
A Berlin U-Bahn station is an underground or elevated public transit facility in Berlin that serves as a stop for the city’s metro trains, providing passenger access, ticketing, and connections to other transport modes.
-
D.
AeroTrain station
An AeroTrain station is a designated facility where passengers board, disembark, and transfer between AeroTrains, providing platforms, ticketing, waiting areas, and related services for high-speed or automated airport rail transit.
-
E.
railway bridge terminus
A railway bridge terminus is the endpoint of a rail line where tracks transition from or onto a bridge structure, often incorporating platforms, signaling, and facilities for train arrival, departure, and turnaround.
- 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_69bd43e9b88481908582103dcadff3d9 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:17 p.m.