Triple
T15171413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nearby APIs |
E362493
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | proximity communication framework |
C36054
|
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: proximity communication framework Context triple: [Nearby APIs, instanceOf, proximity communication framework]
-
A.
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.
-
B.
RFID air interface standard
An RFID air interface standard defines the communication protocols, signal characteristics, and data exchange rules between RFID tags and readers over the wireless radio frequency link.
-
C.
contactless access system
A contactless access system is a security solution that grants or denies entry to users through non-physical interaction methods such as RFID cards, mobile credentials, or biometrics, enhancing convenience and hygiene while maintaining controlled access.
-
D.
EPCglobal network service
EPCglobal network service is a standardized infrastructure that enables secure sharing, lookup, and retrieval of EPC-related product and event data across organizations in a supply chain.
-
E.
Bluetooth Low Energy security feature
A Bluetooth Low Energy security feature is a mechanism or protocol that protects BLE communications by providing authentication, encryption, integrity, and privacy between connected devices.
- 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_69d85a087b7c81908baa94a53dac8d68 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:08 a.m.