Triple
T24296836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System One travelcards |
E605982
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | integrated ticketing product |
C13844
|
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: integrated ticketing product Context triple: [System One travelcards, instanceOf, integrated ticketing product]
-
A.
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.
-
B.
ticketing facility
A ticketing facility is a system or location where tickets are created, managed, and distributed for events, services, or transportation, handling reservations, payments, and access control.
-
C.
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.
-
D.
transit fare product
chosen
A transit fare product is a purchasable medium (such as a ticket, pass, or stored value) that grants a rider the right to access and use public transportation services under specified conditions.
-
E.
public transport ticket
A public transport ticket is a proof-of-payment token, physical or digital, that grants an individual the right to use specified public transportation services for a defined route, time period, or fare zone.
- 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_69e29549335881909cbf27adcaba1cf0 |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 18, 2026, 12:09 a.m.