Triple
T23107049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BST (Glasgow Subway internal code) |
E576197
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | transportation system internal code |
C31499
|
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: transportation system internal code Context triple: [BST (Glasgow Subway internal code), instanceOf, transportation system internal code]
-
A.
public transport information system
A public transport information system is a software platform that collects, processes, and disseminates real-time and scheduled data about public transit services to passengers, operators, and other stakeholders.
-
B.
public transport ticketing system
A public transport ticketing system manages the purchase, validation, and tracking of fares and passes for passengers across various transit services.
-
C.
transit operator code
chosen
A transit operator code is a standardized identifier assigned to a public transportation agency or company, used to uniquely reference and manage its services within transit systems and data exchanges.
-
D.
integrated transportation and hospitality system
An integrated transportation and hospitality system is a coordinated network that seamlessly combines travel services (such as flights, trains, and local transit) with lodging, amenities, and guest services into a unified, end-to-end customer experience.
-
E.
streetcar system
A streetcar system is an urban public transit network that operates rail vehicles on fixed tracks, typically embedded in city streets, to transport passengers along defined routes.
- 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_69e245f4af548190898d434a64a1e774 |
completed | April 17, 2026, 2:38 p.m. |
Created at: April 17, 2026, 3:58 p.m.