Triple
T27756232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melissa virus |
E701338
|
entity |
| Predicate | payloadTrigger |
P872
|
FINISHED |
| Object | opening an infected Word document |
—
|
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: opening an infected Word document | Statement: [Melissa virus, payloadTrigger, opening an infected Word document]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: payloadTrigger Context triple: [Melissa virus, payloadTrigger, opening an infected Word document]
-
A.
trigger
Indicates that one entity causes or initiates an event, state, or action in another entity or system.
-
B.
triggered
Indicates that one entity causes an event, action, or process involving another entity to start or occur.
-
C.
triggerEvent
chosen
Indicates that one entity causes or initiates the occurrence of a specific event involving another entity or the system.
-
D.
trapTrigger
Indicates that an entity activates or sets off a trap in the environment.
-
E.
payloadAction
Indicates an action performed on, with, or involving a payload (such as creating, sending, modifying, or processing it).
- 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_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 4:23 p.m.