Triple
T4073932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breeze Mobile |
E86715
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mobile ticketing application |
C8881
|
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: mobile ticketing application Context triple: [Breeze Mobile, instanceOf, mobile ticketing application]
-
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
chosen
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.
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.
-
D.
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.
-
E.
fare card
A fare card is a reusable, often electronic, payment token used to access and pay for rides on public transportation systems.
- 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_69aed93ebe448190a1f1686e28740ac9 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:39 p.m.