Triple
T31080822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heartbleed |
E792089
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | information disclosure vulnerability |
C58819
|
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: information disclosure vulnerability Context triple: [Heartbleed, instanceOf, information disclosure vulnerability]
-
A.
intelligence leak
An intelligence leak is the unauthorized disclosure of sensitive or classified information, often compromising operations, sources, or national security.
-
B.
vulnerability database
A vulnerability database is a structured repository that collects, organizes, and provides information about known security weaknesses in software, hardware, and systems to support risk assessment and remediation.
-
C.
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.
-
D.
public disclosure system
A public disclosure system is a structured mechanism for collecting, verifying, and openly publishing information so that stakeholders and the general public can access and evaluate it for transparency and accountability.
-
E.
security-related information service
A security-related information service is a system that collects, analyzes, and disseminates data about threats, vulnerabilities, and protective measures to help users or organizations enhance their security posture.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:02 p.m.