Triple
T5156396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RC6 |
E116319
|
entity |
| Predicate | usesKeyScheduleFrom |
P60607
|
FINISHED |
| Object | RC5-like key schedule |
—
|
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: RC5-like key schedule | Statement: [RC6, usesKeyScheduleFrom, RC5-like key schedule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesKeyScheduleFrom Context triple: [RC6, usesKeyScheduleFrom, RC5-like key schedule]
-
A.
keyExpansion
chosen
Indicates the process of deriving a set of subkeys from an original key for use in a cryptographic algorithm.
-
B.
usesInitializationVectorLength
Indicates that an entity employs an initialization vector (IV) of a specified length in a cryptographic or security-related operation.
-
C.
usesEncryptionAlgorithm
Indicates that one entity applies or relies on a specific encryption algorithm to protect data or communications.
-
D.
cipherKey
Indicates that one entity serves as the cryptographic key used to encrypt or decrypt information associated with another entity.
-
E.
keyDerivation
Indicates that one cryptographic key is generated or derived from another key or base secret using a specific derivation 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_69bd445d94788190b72e2cc563120995 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79c1354c81908176703b4853c1a4 |
completed | March 20, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69bd77b0fbb88190851e2d7ae1bdcc09 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:44 p.m.