Triple
T23363167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 5G AKA |
E593239
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mobile network security protocol |
C995
|
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 network security protocol Context triple: [5G AKA, instanceOf, mobile network security protocol]
-
A.
network security protocol
chosen
A network security protocol is a defined set of rules and procedures that protect data integrity, confidentiality, and authenticity during communication between devices over a network.
-
B.
mobile core network protocol
A mobile core network protocol is a set of standardized rules and procedures that govern how data, signaling, and control information are exchanged within the core of a mobile communication network to enable connectivity, mobility, and services for users.
-
C.
mobile network interface
A mobile network interface is a hardware and software component that enables a device to connect to and communicate over cellular networks for voice, data, and messaging services.
-
D.
mobile security service
A mobile security service is a system that protects mobile devices, applications, and data from threats through features like malware detection, secure communication, access control, and real-time monitoring.
-
E.
secure communications network
A secure communications network is a system of interconnected devices and infrastructure that transmits data using encryption, authentication, and access controls to ensure confidentiality, integrity, and availability of information.
- 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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:30 p.m.