Triple
T1500514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Advanced Encryption Standard |
E29784
|
entity |
| Predicate | encryptionType |
P21840
|
FINISHED |
| Object | symmetric |
—
|
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: symmetric | Statement: [Advanced Encryption Standard, encryptionType, symmetric]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encryptionType Context triple: [Advanced Encryption Standard, encryptionType, symmetric]
-
A.
usesEncryptionAlgorithm
Indicates that one entity applies or relies on a specific encryption algorithm to protect data or communications.
-
B.
encryptionDirection
Indicates the direction in which data is being encrypted, specifying whether it is going from source to destination or vice versa.
-
C.
cipherCategory
Indicates that one item is classified as a type or category of cipher to which the other item belongs.
-
D.
requiresEncryption
Indicates that one entity must use encryption when communicating with, storing data for, or otherwise interacting with another entity.
-
E.
algorithmType
chosen
Indicates the specific kind or category of algorithm associated with an entity or process.
- 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_69a498dba1d8819093b46a3a8d2485f1 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6f2d7f881909188a3e5614335cd |
completed | March 1, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69a4c48a8cf48190a6ebf8d44a608a06 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:12 p.m.