Triple
T27756107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love Letter worm |
E701335
|
entity |
| Predicate | inspiredSecurityResponse |
P120037
|
FINISHED |
| Object | stricter email attachment filtering policies |
—
|
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: stricter email attachment filtering policies | Statement: [Love Letter worm, inspiredSecurityResponse, stricter email attachment filtering policies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inspiredSecurityResponse Context triple: [Love Letter worm, inspiredSecurityResponse, stricter email attachment filtering policies]
-
A.
securityResponse
chosen
Indicates how an entity reacts or takes action in response to a security-related event, threat, or condition.
-
B.
securedAgainst
Indicates that one entity is protected or safeguarded against threats, risks, or harmful actions originating from another entity or source.
-
C.
helpedSecure
Indicates that one entity contributed to obtaining, protecting, or ensuring the safety or stability of another entity or outcome.
-
D.
securityOutcome
Indicates the result or consequence of a security-related event, measure, or decision for the involved entities.
-
E.
securityAdvisory
Indicates a relationship where an entity issues, references, or is associated with a warning or guidance about security vulnerabilities, risks, or protective measures.
- 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_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 27, 2026, 4:23 p.m.