Triple
T31080863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heartbleed |
E792089
|
entity |
| Predicate | CVSSv2ExploitabilitySubscore |
P171332
|
FINISHED |
| Object | 10.0 |
—
|
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: 10.0 | Statement: [Heartbleed, CVSSv2ExploitabilitySubscore, 10.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CVSSv2ExploitabilitySubscore Context triple: [Heartbleed, CVSSv2ExploitabilitySubscore, 10.0]
-
A.
canBeExploitedRemotely
Indicates that the vulnerability or weakness can be triggered and abused from a distance over a network, without requiring physical access to the target system.
-
B.
vulnerabilityType
Indicates the specific kind or category of vulnerability associated with an entity or situation.
-
C.
CVEIdentifier
Indicates that an entity is associated with a specific Common Vulnerabilities and Exposures (CVE) identifier, uniquely referencing a documented security vulnerability.
-
D.
vulnerabilitySource
Indicates that one entity is the origin, cause, or contributing factor of another entity’s vulnerability or weakness.
-
E.
attackComplexity
Indicates the level of difficulty or effort required by an attacker to successfully exploit a vulnerability or carry out an attack.
- F. None of above. chosen
Provenance (4 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_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69dfbf6ac8190ba2e6fc0adfd8b73 |
completed | May 3, 2026, 12:59 a.m. |
Created at: April 29, 2026, 9:02 p.m.