Triple
T27613447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JSON Web Encryption |
E700378
|
entity |
| Predicate | supportsContentEncryptionAlgorithmType |
P5656
|
FINISHED |
| Object | AES GCM |
—
|
NE NERFINISHED |
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: AES GCM | Statement: [JSON Web Encryption, supportsContentEncryptionAlgorithmType, AES GCM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsContentEncryptionAlgorithmType Context triple: [JSON Web Encryption, supportsContentEncryptionAlgorithmType, AES GCM]
-
A.
usesEncryptionAlgorithm
chosen
Indicates that one entity applies or relies on a specific encryption algorithm to protect data or communications.
-
B.
canBeEncryptedUsing
Indicates that one entity is capable of being transformed into a secure, encoded form by applying the encryption method or key represented by another entity.
-
C.
encryptionModeSupport
Indicates that an entity supports or is compatible with a specified mode of encryption.
-
D.
supportsHardwareCryptography
Indicates that one entity provides or enables hardware-based cryptographic operations or capabilities for another entity.
-
E.
supportsKeyManagementProtocol
Indicates that one entity is capable of using or is compatible with a specified key management protocol for handling cryptographic keys.
- 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_69ff65987ff88190b09be64f7c0e1da9 |
completed | May 9, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69ff6525b0548190bef7a9f009e00bb8 |
completed | May 9, 2026, 4:47 p.m. |
Created at: April 27, 2026, 2:12 p.m.