Triple
T23107048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BST (Glasgow Subway internal code) |
E576197
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Glasgow Subway station code |
C47237
|
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: Glasgow Subway station code Context triple: [BST (Glasgow Subway internal code), instanceOf, Glasgow Subway station code]
-
A.
Glasgow Subway fare zone
A Glasgow Subway fare zone is a designated geographic area within the subway network used to determine ticket prices and valid travel boundaries for passengers.
-
B.
New York City Subway station code
A New York City Subway station code is a unique alphanumeric identifier assigned to each subway station to standardize reference, operations, and data management across the transit system.
-
C.
railway station code
A railway station code is a short alphanumeric identifier assigned to a specific train station to uniquely reference it in timetables, ticketing, and railway operations.
-
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.
railway station in Scotland
A railway station in Scotland is a designated facility along the Scottish rail network where trains stop to allow passengers to board and alight, often providing ticketing, waiting areas, and connections to local transport services.
- 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_69e245f4af548190898d434a64a1e774 |
completed | April 17, 2026, 2:38 p.m. |
Created at: April 17, 2026, 3:58 p.m.