Triple
T33434515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Web Cryptography API |
E856209
|
entity |
| Predicate | supportsKeyUsages |
—
|
GENERATED |
| Object | encrypt |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsKeyUsages Context triple: [Web Cryptography API, supportsKeyUsages, encrypt]
-
A.
hasKeyUsage
chosen
Indicates that an entity (such as a key or certificate) is associated with a specific intended purpose or allowed type of usage.
-
B.
supportsKeyManagementProtocol
Indicates that one entity is capable of using or is compatible with a specified key management protocol for handling cryptographic keys.
-
C.
supportsX509
Indicates that one entity is capable of handling, recognizing, or operating with X.509 certificates in its interactions or operations with another entity.
-
D.
supportsKeyManagement
Indicates that one entity provides functionality or capability to handle, store, or control cryptographic keys for another entity or process.
-
E.
supportsMultipleCertificates
Indicates that an entity is capable of handling, storing, or operating with more than one certificate simultaneously.
- F. None of above.
Provenance (1 batch)
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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:36 a.m.