Triple
T7895120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ILOVEYOU worm |
E183324
|
entity |
| Predicate | fileTypeMasquerade |
P79630
|
FINISHED |
| Object | pretended to be a text file |
—
|
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: pretended to be a text file | Statement: [ILOVEYOU worm, fileTypeMasquerade, pretended to be a text file]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fileTypeMasquerade Context triple: [ILOVEYOU worm, fileTypeMasquerade, pretended to be a text file]
-
A.
fileTypeIIDMeaning
Indicates that the predicate specifies the meaning or interpretation associated with a particular file type identifier (IID).
-
B.
fileTypeCIDMeaning
Indicates the specific meaning or interpretation associated with a file type identified by its CID (Content Identifier).
-
C.
mediaType
Indicates the format or category of media associated with an entity, such as text, image, audio, or video.
-
D.
pegType
Indicates the specific category or kind of peg associated with or assigned to an entity.
-
E.
hasFileFormat
Indicates that one entity (typically a digital file or resource) is encoded, stored, or represented using a specific file format defined by 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_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. |
| PDg | Predicate description generation | batch_69caf786ec748190b6347b0c94335550 |
completed | March 30, 2026, 10:21 p.m. |
Created at: March 30, 2026, 5:01 p.m.