Triple
T27756126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love Bug |
E701336
|
entity |
| Predicate | usesSocialEngineering |
P127624
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Love Bug, usesSocialEngineering, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSocialEngineering Context triple: [Love Bug, usesSocialEngineering, yes]
-
A.
usesSocialEngineeringTheme
Indicates that an action or communication employs social engineering tactics or themes to influence, deceive, or manipulate a target.
-
B.
usedMeansOfDeception
chosen
Indicates that one entity employed a particular method or tool specifically to deceive another entity.
-
C.
isExploitedFor
Indicates that one entity is unfairly or abusively used by another entity as a resource, means, or advantage for the latter’s benefit.
-
D.
canBeExploitedFor
Indicates that one entity is capable of being used or taken advantage of by another entity to obtain some benefit, resource, or outcome.
-
E.
exploits
Indicates that one entity unfairly or selfishly uses another entity or resource for its own advantage or benefit.
- 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_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 27, 2026, 4:23 p.m.