Triple
T34061207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hybrid Public Key Encryption |
E873495
|
entity |
| Predicate | canUseAEAD |
P76803
|
FINISHED |
| Object | AES-128-GCM |
—
|
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: AES-128-GCM | Statement: [Hybrid Public Key Encryption, canUseAEAD, AES-128-GCM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canUseAEAD Context triple: [Hybrid Public Key Encryption, canUseAEAD, AES-128-GCM]
-
A.
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.
-
B.
encryptionModeSupport
chosen
Indicates that an entity supports or is compatible with a specified mode of encryption.
-
C.
supportsHardwareCryptography
Indicates that one entity provides or enables hardware-based cryptographic operations or capabilities for another entity.
-
D.
usesEncryptionAlgorithm
Indicates that one entity applies or relies on a specific encryption algorithm to protect data or communications.
-
E.
combinedAsAEADWith
Indicates that two cryptographic components (typically an encryption algorithm and an authentication mechanism) are used together to form an AEAD (Authenticated Encryption with Associated Data) construction.
- 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_69f349a4af208190afa14888f9c9fb9d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:52 a.m.