Triple
T165938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wired Equivalent Privacy |
E3014
|
entity |
| Predicate | usesKeyType |
P1150
|
FINISHED |
| Object | static symmetric key |
—
|
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: static symmetric key | Statement: [Wired Equivalent Privacy, usesKeyType, static symmetric key]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesKeyType Context triple: [Wired Equivalent Privacy, usesKeyType, static symmetric key]
-
A.
typicalKey
chosen
Indicates that the referenced key is the standard or most commonly used key associated with an entity or context.
-
B.
usageType
Indicates the specific manner, purpose, or context in which something is used or intended to be used.
-
C.
securityType
Indicates the classification or category of security associated with an entity, such as the type of financial instrument, protection mechanism, or access control applied.
-
D.
usedEvidenceType
Indicates that a particular type or category of evidence was employed or relied upon in a given context or activity.
-
E.
usesStandard
Indicates that one entity adopts, follows, or operates according to a specified standard defined by another entity or reference.
- 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_69a2524ce1e48190ab066bf72859f474 |
completed | Feb. 28, 2026, 2:26 a.m. |
| NER | Named-entity recognition | batch_69a25883ac8481909616b2179561bd98 |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a25664ba8081908ac298511a9fc5ba |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:34 a.m.