Triple
T27756212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melissa virus |
E701338
|
entity |
| Predicate | malwareType |
P18419
|
FINISHED |
| Object | macro virus |
—
|
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: macro virus | Statement: [Melissa virus, malwareType, macro virus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: malwareType Context triple: [Melissa virus, malwareType, macro virus]
-
A.
notableMalware
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.
systemThreatType
Indicates the category or nature of threat that a system poses or is exposed to.
-
C.
vulnerabilityType
Indicates the specific kind or category of vulnerability associated with an entity or situation.
-
D.
virusSubtype
chosen
Indicates the specific subtype classification of a virus within a broader virus type or strain.
-
E.
isTrojanOf
Indicates that one entity is a Trojan (e.g., a malicious or deceptive program or component) specifically associated with, derived from, or targeting another entity.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63760b350819088f0eca0257ca125 |
completed | May 2, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 4:23 p.m.