Triple
T27692262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TLS heartbeat extension |
E698189
|
entity |
| Predicate | associatedVulnerability |
P67454
|
FINISHED |
| Object | Heartbleed |
—
|
NE NERFINISHED |
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: Heartbleed | Statement: [TLS heartbeat extension, associatedVulnerability, Heartbleed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedVulnerability Context triple: [TLS heartbeat extension, associatedVulnerability, Heartbleed]
-
A.
associatedWithVulnerability
chosen
Indicates a relationship where an entity is linked to, affected by, or relevant to a specific vulnerability or security weakness.
-
B.
CVEIdentifier
Indicates that an entity is associated with a specific Common Vulnerabilities and Exposures (CVE) identifier, uniquely referencing a documented security vulnerability.
-
C.
securityVulnerability
Indicates that an entity has a weakness or flaw that could be exploited to compromise its security.
-
D.
vulnerabilitySource
Indicates that one entity is the origin, cause, or contributing factor of another entity’s vulnerability or weakness.
-
E.
vulnerabilityType
Indicates the specific kind or category of vulnerability associated with an entity or situation.
- 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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_6a0056174c908190be99c91a70393e47 |
completed | May 10, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_6a00538e7e08819091ecd4316cd641a1 |
completed | May 10, 2026, 9:44 a.m. |
Created at: April 27, 2026, 2:52 p.m.