Triple
T21191290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MOBIKE |
E522216
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | VPN mobility protocol |
C5251
|
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: VPN mobility protocol Context triple: [MOBIKE, instanceOf, VPN mobility protocol]
-
A.
virtual private network software
Virtual private network software is an application that securely routes a user's internet traffic through encrypted tunnels via remote servers to protect privacy, enhance security, and enable access to restricted or geo-blocked resources.
-
B.
mobility management protocol
chosen
A mobility management protocol is a set of rules and procedures that enables devices to maintain seamless network connectivity and consistent addressing while moving across different networks or access points.
-
C.
NAT traversal framework
A NAT traversal framework is a software system that provides reusable mechanisms and protocols to enable networked applications to establish and maintain connections across Network Address Translation (NAT) boundaries.
-
D.
IPsec extension
An IPsec extension is a conceptual class that augments core IPsec functionality with additional security, configuration, or protocol features to support enhanced or specialized network protection requirements.
-
E.
network security protocol
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.
- 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 3:07 p.m.