Triple
T31080823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heartbleed |
E792089
|
entity |
| Predicate | CVEID |
P165911
|
FINISHED |
| Object | CVE-2014-0160 |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: CVE-2014-0160 | Statement: [Heartbleed, CVEID, CVE-2014-0160]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CVEID Context triple: [Heartbleed, CVEID, CVE-2014-0160]
-
A.
CVEIdentifier
chosen
Indicates that an entity is associated with a specific Common Vulnerabilities and Exposures (CVE) identifier, uniquely referencing a documented security vulnerability.
-
B.
vulnerabilityType
Indicates the specific kind or category of vulnerability associated with an entity or situation.
-
C.
associatedWithVulnerability
Indicates a relationship where an entity is linked to, affected by, or relevant to a specific vulnerability or security weakness.
-
D.
vulnerabilitySource
Indicates that one entity is the origin, cause, or contributing factor of another entity’s vulnerability or weakness.
-
E.
designatedVariantOfConcernBy
Indicates that an entity has been officially classified as a Variant of Concern by a specified authority or organization.
- F. None of above.
Provenance (3 batches)
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. |
| NER | Named-entity recognition | batch_69f695f9fe7c819084322bf6cdc70a13 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
Created at: April 29, 2026, 9:02 p.m.