Triple
T27756087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love Letter worm |
E701335
|
entity |
| Predicate | targetedFileExtensions |
P180408
|
FINISHED |
| Object | .vbs |
—
|
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: .vbs | Statement: [Love Letter worm, targetedFileExtensions, .vbs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetedFileExtensions Context triple: [Love Letter worm, targetedFileExtensions, .vbs]
-
A.
introducedFileExtension
Indicates that an entity caused a particular file extension to be created, defined, or brought into use.
-
B.
includesExtension
Indicates that one entity contains or incorporates another entity as an added or supplementary extension.
-
C.
supportsExtensionsFrom
Indicates that one entity is capable of recognizing, loading, or interoperating with extensions originating from another entity.
-
D.
containerFilenameExtension
Indicates that one item is a filename extension associated with a particular container format.
-
E.
typicalFileType
Indicates that one entity is the usual or commonly associated file type for the other entity.
- F. None of above. chosen
Provenance (4 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_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
| PDg | Predicate description generation | batch_69f74061c440819080434155c2d60341 |
completed | May 3, 2026, 12:32 p.m. |
Created at: April 27, 2026, 4:23 p.m.