Triple
T19352532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wi‑Fi Protected Setup |
E484056
|
entity |
| Predicate | canBeExploitedRemotely |
P135210
|
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: [Wi‑Fi Protected Setup, canBeExploitedRemotely, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeExploitedRemotely Context triple: [Wi‑Fi Protected Setup, canBeExploitedRemotely, yes]
-
A.
vulnerabilityType
Indicates the specific kind or category of vulnerability associated with an entity or situation.
-
B.
vulnerabilitySource
Indicates that one entity is the origin, cause, or contributing factor of another entity’s vulnerability or weakness.
-
C.
earlyExploitationBy
Indicates that one entity takes unfair advantage of another at an early stage of their interaction, development, or process.
-
D.
abusePubliclyExposed
Indicates that one entity mistreats, exploits, or harms another entity whose sensitive information or vulnerabilities have been made publicly accessible.
-
E.
exploits
Indicates that one entity unfairly or selfishly uses another entity or resource for its own advantage or benefit.
- 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_69d8e8d244f8819080eb1f3491300db2 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e61905b16881909ab0e932bb9a0cda |
completed | April 20, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69e4dd13a8cc81909cd02668564c9f29 |
completed | April 19, 2026, 1:48 p.m. |
| PDg | Predicate description generation | batch_69e4dde92ff481909006b3f9e8d639d4 |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 1:34 p.m.