Triple
T6414380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | unireso |
E127786
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | integrated ticketing system |
C4038
|
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 system Context triple: [unireso, instanceOf, integrated ticketing system]
-
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.
ticketing zone
A ticketing zone is a designated area within a transportation or event system where specific fare or access rules apply, determining the validity and cost of tickets used within its boundaries.
-
D.
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.
-
E.
public transit fare payment system
chosen
A public transit fare payment system manages the calculation, collection, validation, and tracking of passenger payments across various transit services and media (e.g., cards, mobile apps, tickets) to authorize and record travel.
- 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_69c0083815208190a9b299b8e0640218 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 4:42 p.m.