Triple
T31080821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heartbleed |
E792089
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | OpenSSL vulnerability |
C27007
|
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: OpenSSL vulnerability Context triple: [Heartbleed, instanceOf, OpenSSL vulnerability]
-
A.
transport layer security vulnerability
A transport layer security vulnerability is a weakness in the protocols, configurations, or implementations that protect data in transit, allowing attackers to intercept, decrypt, modify, or impersonate secure communications.
-
B.
software vulnerability advisory
A software vulnerability advisory is an official notice that describes a security flaw in software, its potential impact, affected versions, and recommended mitigation or remediation steps.
-
C.
Insecure-related topic
An insecure-related topic is any subject, situation, or issue that triggers feelings of self-doubt, vulnerability, or inadequacy in an individual or group.
-
D.
U.S. government encryption standard
A U.S. government encryption standard is an officially approved cryptographic algorithm or protocol, such as AES, mandated or recommended by federal authorities to protect sensitive government and public-sector information.
-
E.
cryptographic library
chosen
A cryptographic library is a collection of software routines that implement cryptographic algorithms and protocols to provide secure encryption, decryption, hashing, key management, and related security functions for applications.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:02 p.m.