Triple
T27692266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TLS heartbeat extension |
E698189
|
entity |
| Predicate | vulnerabilityImpact |
P103390
|
FINISHED |
| Object | potential exposure of private keys |
—
|
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: potential exposure of private keys | Statement: [TLS heartbeat extension, vulnerabilityImpact, potential exposure of private keys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vulnerabilityImpact Context triple: [TLS heartbeat extension, vulnerabilityImpact, potential exposure of private keys]
-
A.
integrityImpact
Indicates the extent to which the relationship or action compromises, alters, or destroys the accuracy, consistency, or trustworthiness of the affected entity’s information or state.
-
B.
impactDescription
chosen
Indicates a description of the effect, consequence, or influence that one entity, action, or event has on another.
-
C.
impactLevel
Indicates the degree or intensity of effect that one entity, action, or event has on another.
-
D.
vulnerabilityType
Indicates the specific kind or category of vulnerability associated with an entity or situation.
-
E.
strategicVulnerability
Indicates a relationship where an entity is exposed to potential harm or disadvantage in a way that can be deliberately exploited within a strategic or competitive context.
- 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_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 2:52 p.m.