Triple
T3778492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunderland station |
E83364
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tyne and Wear Metro station |
C2851
|
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: Tyne and Wear Metro station Context triple: [Sunderland station, instanceOf, Tyne and Wear Metro station]
-
A.
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.
-
B.
public transit station
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.
light-rail station
chosen
A light-rail station is a designated facility where light-rail vehicles stop to allow passengers to board, alight, and transfer between services, typically featuring platforms, shelters, signage, and ticketing amenities.
-
D.
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.
-
E.
monorail station
A monorail station is a designated facility where passengers board, alight, and transfer to monorail trains, typically featuring elevated platforms, access structures, and passenger amenities.
- 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_69ad8b235e608190b5a2b1d1bfcef50b |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:36 p.m.