Triple
T7895094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ILOVEYOU worm |
E183324
|
entity |
| Predicate | socialEngineeringTechnique |
P5659
|
FINISHED |
| Object | fake love letter |
—
|
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: fake love letter | Statement: [ILOVEYOU worm, socialEngineeringTechnique, fake love letter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socialEngineeringTechnique Context triple: [ILOVEYOU worm, socialEngineeringTechnique, fake love letter]
-
A.
attackToolExample
chosen
Indicates that a specific tool or method is used as an example of how an attack is or can be carried out.
-
B.
exploits
Indicates that one entity unfairly or selfishly uses another entity or resource for its own advantage or benefit.
-
C.
earlyExploitationBy
Indicates that one entity takes unfair advantage of another at an early stage of their interaction, development, or process.
-
D.
attackType
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
-
E.
attackProfile
Indicates a relationship where one entity initiates or carries out an aggressive or hostile action against 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_69ca828c474c8190a254d6499871eaff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a174574819084270dbb6fcbb7fe |
completed | March 31, 2026, 3:05 a.m. |
| PD | Predicate disambiguation | batch_69cae92d94448190b4425bbfb64c658c |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:01 p.m.