Triple
T5085184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RC5 |
E114618
|
entity |
| Predicate | blockCipherType |
P21843
|
FINISHED |
| Object | word-oriented block cipher |
—
|
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: word-oriented block cipher | Statement: [RC5, blockCipherType, word-oriented block cipher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blockCipherType Context triple: [RC5, blockCipherType, word-oriented block cipher]
-
A.
cipherCategory
chosen
Indicates that one item is classified as a type or category of cipher to which the other item belongs.
-
B.
cryptDesigner
Indicates that an entity is the designer or creator responsible for planning or conceiving a particular crypt.
-
C.
ciphertextExpansion
Indicates that applying the encryption process to the input increases its length, specifying how much the ciphertext expands relative to the original data.
-
D.
cryptographicModel
Indicates a relationship where one entity serves as, or is based on, a particular cryptographic scheme, framework, or formal model.
-
E.
usesEncryptionAlgorithm
Indicates that one entity applies or relies on a specific encryption algorithm to protect data or communications.
- 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_69bd443e941881908eb4e8c685b6f656 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75192d188190a7631bce5faf7de3 |
completed | March 20, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69bd7159adc881909effd4382c395c66 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:40 p.m.