Triple
T32733449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unit 74455 |
E837014
|
entity |
| Predicate | associatedMalware |
—
|
GENERATED |
| Object | BlackEnergy |
—
|
UNRECOGNIZED GENERATED |
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedMalware Context triple: [Unit 74455, associatedMalware, BlackEnergy]
-
A.
notableMalware
chosen
Indicates that the entity is recognized as a significant or well-known piece of malware, often due to its impact, prevalence, or technical characteristics.
-
B.
associatedIntrusionType
Indicates that one entity is linked to, or characterized by, a particular type or category of intrusion.
-
C.
associatedWithVulnerability
Indicates a relationship where an entity is linked to, affected by, or relevant to a specific vulnerability or security weakness.
-
D.
relatedAttack
Indicates that one attack is connected or associated with another attack, such as being part of the same incident, campaign, or sequence of actions.
-
E.
associatedWithVirusSpecies
Indicates a relationship where one entity is linked or connected to a particular virus species, typically through relevance, involvement, or attribution.
- F. None of above.
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_69f34935fb048190ad4967420581f835 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:11 a.m.