Triple
T5834350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wi‑Fi CERTIFIED WPA2 |
E129431
|
entity |
| Predicate | supportsKeyManagementProtocol |
P67453
|
FINISHED |
| Object | 4‑way handshake |
—
|
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: 4‑way handshake | Statement: [Wi‑Fi CERTIFIED WPA2, supportsKeyManagementProtocol, 4‑way handshake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsKeyManagementProtocol Context triple: [Wi‑Fi CERTIFIED WPA2, supportsKeyManagementProtocol, 4‑way handshake]
-
A.
keyManagementType
Indicates the method or scheme by which cryptographic keys are generated, stored, distributed, and controlled within a system or process.
-
B.
supportsKeyLength
Indicates that one entity is capable of handling, accepting, or operating with a specified cryptographic key length associated with another entity.
-
C.
hasKeyInfrastructure
Indicates that an entity possesses or is associated with essential infrastructure components critical for its operation or function.
-
D.
isKeyTransitHub
Indicates that a location functions as a major transfer point where multiple transportation routes or modes intersect and a high volume of passenger or cargo movement is concentrated.
-
E.
hasKeyAgreement
Indicates that two parties share or have established a cryptographic key agreement used to securely derive a common secret key.
- 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_69c0084af79c81908af128ccc29983d0 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ab0a048190b84be40fb13c0f50 |
completed | March 22, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c03341e5888190a5f219b6f92cb161 |
completed | March 22, 2026, 6:21 p.m. |
| PDg | Predicate description generation | batch_69c044a9c4f0819081b8c196932883f6 |
completed | March 22, 2026, 7:36 p.m. |
Created at: March 22, 2026, 3:54 p.m.