Triple
T19352519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wi‑Fi Protected Setup |
E484056
|
entity |
| Predicate | affectedDevice |
P86660
|
FINISHED |
| Object | wireless routers |
—
|
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: wireless routers | Statement: [Wi‑Fi Protected Setup, affectedDevice, wireless routers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectedDevice Context triple: [Wi‑Fi Protected Setup, affectedDevice, wireless routers]
-
A.
relatedToDevice
Indicates that there exists a general association or connection between an entity and a device, without specifying the exact nature of that relationship.
-
B.
relatedDevice
Indicates that one device has an association or connection to another device, without specifying the exact nature of that relationship.
-
C.
targetedDevice
chosen
Indicates that one entity is the specific device toward which another entity’s action, effect, or configuration is directed.
-
D.
testedDevice
Indicates that one entity has performed a test on, or experimentally evaluated, another entity as a device.
-
E.
usedAsDeviceFor
Indicates that one entity functions as a tool, instrument, or device for performing an action or achieving a particular purpose for another entity.
- 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_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. |
Created at: April 10, 2026, 1:34 p.m.