Triple
T1061946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wi‑Fi CERTIFIED WPA3 |
E22925
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Wi‑Fi security certification program |
C6046
|
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: Wi‑Fi security certification program Context triple: [Wi‑Fi CERTIFIED WPA3, instanceOf, Wi‑Fi security certification program]
-
A.
wireless communication device
A wireless communication device is an electronic apparatus that transmits and receives data over radio or other non-wired signals to enable voice, text, or multimedia communication without physical connections.
-
B.
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.
-
C.
peer-to-peer electronic cash system
A peer-to-peer electronic cash system is a decentralized digital payment network that allows users to send value directly to one another over the internet without relying on trusted intermediaries like banks or payment processors.
-
D.
IETF document series
The IETF document series is a collection of technical publications, including RFCs and Internet-Drafts, that specify, document, and standardize protocols, procedures, and best practices for the Internet.
-
E.
internet protocol suite
The internet protocol suite is a conceptual framework of layered communication protocols (including TCP/IP) that defines how data is formatted, addressed, transmitted, routed, and received across interconnected computer networks.
- 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_69a493dada0481909c43649f9843ea91 |
completed | March 1, 2026, 7:30 p.m. |
Created at: March 1, 2026, 7:42 p.m.