Triple
T23312872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TAXII |
E590628
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cybersecurity protocol |
C994
|
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: cybersecurity protocol Context triple: [TAXII, instanceOf, cybersecurity protocol]
-
A.
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.
-
B.
cybersecurity system
A cybersecurity system is an integrated set of tools, policies, and processes designed to protect digital assets, networks, and data from unauthorized access, attacks, and damage.
-
C.
cryptographic protocol
chosen
A cryptographic protocol is a precisely defined sequence of operations and message exchanges that uses cryptographic primitives to achieve security goals such as confidentiality, integrity, authentication, and non-repudiation between parties.
-
D.
security practice
A security practice is a repeatable method, process, or behavior designed to protect systems, data, and users from threats and vulnerabilities.
-
E.
security program
A security program is an organized set of policies, processes, technologies, and resources designed to protect an organization’s assets, information, and operations from threats and vulnerabilities.
- 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_69e25d1d32188190948eb76909d1dcc3 |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:06 p.m.