Triple
T27613442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JSON Web Encryption |
E700378
|
entity |
| Predicate | supportsKeyManagementAlgorithmType |
P105564
|
FINISHED |
| Object | asymmetric key encryption |
—
|
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: asymmetric key encryption | Statement: [JSON Web Encryption, supportsKeyManagementAlgorithmType, asymmetric key encryption]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsKeyManagementAlgorithmType Context triple: [JSON Web Encryption, supportsKeyManagementAlgorithmType, asymmetric key encryption]
-
A.
supportsKeyManagementProtocol
Indicates that one entity is capable of using or is compatible with a specified key management protocol for handling cryptographic keys.
-
B.
supportsKeyManagement
chosen
Indicates that one entity provides functionality or capability to handle, store, or control cryptographic keys for another entity or process.
-
C.
keyManagementType
Indicates the method or scheme by which cryptographic keys are generated, stored, distributed, and controlled within a system or process.
-
D.
keyManagementRequirement
Indicates that there is a specified condition or policy governing how cryptographic keys must be generated, stored, used, rotated, or retired.
-
E.
supportsHardwareCryptography
Indicates that one entity provides or enables hardware-based cryptographic operations or capabilities 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69ff64b957bc81908afbc5914234a8ea |
completed | May 9, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69ff6446593c81909173e296eea2590c |
completed | May 9, 2026, 4:43 p.m. |
Created at: April 27, 2026, 2:12 p.m.