Triple
T13338932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MBTA mTicket mobile app accepted |
E317771
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | digital ticketing platform |
C3843
|
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: digital ticketing platform Context triple: [MBTA mTicket mobile app accepted, instanceOf, digital ticketing platform]
-
A.
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.
-
B.
virtual event management platform
A virtual event management platform is a digital system that enables organizations to plan, host, manage, and analyze online events such as conferences, webinars, and trade shows through integrated tools for registration, content delivery, engagement, and reporting.
-
C.
virtual event management platform
A virtual event management platform is a software system that enables organizations to plan, host, manage, and analyze online events by integrating registration, content delivery, engagement tools, and post-event analytics in a unified digital environment.
-
D.
hybrid event management platform
A hybrid event management platform is a unified system that enables planning, hosting, and analyzing events that combine in-person and virtual experiences, including registration, engagement tools, content delivery, and post-event analytics.
-
E.
public transport ticketing system
chosen
A public transport ticketing system manages the purchase, validation, and tracking of fares and passes for passengers across various transit services.
- 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_69d806b5a3c08190b42c267fb092f98a |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:31 p.m.