Triple
T3856279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disney MagicBand room entry |
E90023
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | contactless access system |
C14407
|
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: contactless access system Context triple: [Disney MagicBand room entry, instanceOf, contactless access system]
-
A.
contactless smart card fare system
A contactless smart card fare system is an electronic payment and access control solution for public transportation that uses proximity cards or devices to automatically deduct fares and manage rider accounts when tapped on compatible readers.
-
B.
contactless smart card standard
A contactless smart card standard defines the technical specifications and communication protocols that enable secure, wireless data exchange between smart cards and readers without physical contact.
-
C.
mandatory access control system
A mandatory access control system is a security model in which access to resources is regulated by a central authority based on predefined policies and security labels, rather than by individual user discretion.
-
D.
contact-type smart card
A contact-type smart card is a plastic card with an embedded integrated circuit chip that must physically connect to a reader via metallic contacts to securely store, process, and exchange data for applications like payments and identification.
-
E.
automated fare gate
An automated fare gate is a mechanized entry barrier system that uses electronic ticket or card validation to control and record passenger access to a paid transit area.
- F. None of above. chosen
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_69aed95b3c088190a8f85d19e6070599 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:19 p.m.