Triple
T19352533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wi‑Fi Protected Setup |
E484056
|
entity |
| Predicate | requiresPhysicalProximity |
P72444
|
FINISHED |
| Object | attacker must be within Wi‑Fi range |
—
|
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: attacker must be within Wi‑Fi range | Statement: [Wi‑Fi Protected Setup, requiresPhysicalProximity, attacker must be within Wi‑Fi range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresPhysicalProximity Context triple: [Wi‑Fi Protected Setup, requiresPhysicalProximity, attacker must be within Wi‑Fi range]
-
A.
physicalRequirement
chosen
Indicates that one entity specifies a necessary physical condition, capability, or resource that must be met or possessed for another entity, action, or process to occur or be valid.
-
B.
hasNearbyAccess
Indicates that one entity has convenient, close-proximity access to another resource, service, or location.
-
C.
nearPass
Indicates that one entity moves or travels close to another entity without necessarily making direct contact or interaction.
-
D.
requiresDevice
Indicates that performing the specified action or relationship is contingent on the presence or use of a particular device.
-
E.
hasProximitySensor
Indicates that an entity is equipped with a sensor capable of detecting nearby objects or measuring its distance to them.
- 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.