Triple
T16000692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pop card (Tyne and Wear Metro) |
E388082
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public transport ticketing medium |
C1449
|
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: public transport ticketing medium Context triple: [Pop card (Tyne and Wear Metro), instanceOf, public transport ticketing medium]
-
A.
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.
-
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.
public transit fare card
chosen
A public transit fare card is a reusable, stored-value or pass-based card that riders use to pay for access to buses, trains, and other public transportation services.
-
D.
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.
-
E.
transit fare product
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.
- 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_69d86daa562c81908aacc179c0fe8fb5 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:55 a.m.