Triple
T27614066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CAST6 |
E700391
|
entity |
| Predicate | blockCipherFamily |
P162749
|
FINISHED |
| Object | CAST family of ciphers |
—
|
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: CAST family of ciphers | Statement: [CAST6, blockCipherFamily, CAST family of ciphers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blockCipherFamily Context triple: [CAST6, blockCipherFamily, CAST family of ciphers]
-
A.
blockCipherStructure
Indicates a relationship where a cryptographic algorithm is organized and operates as a block cipher, processing fixed-size blocks of data under a secret key.
-
B.
blockCipherMode
Indicates the specific operational mode used by a block cipher to process data (e.g., how blocks are chained, padded, or transformed during encryption/decryption).
-
C.
requiresBlockCipher
Indicates that performing this operation or protocol depends on the use of a block cipher as its underlying cryptographic primitive.
-
D.
usesFeistelStructure
Indicates that one entity employs a Feistel network structure as the core design of its cryptographic or transformation process.
-
E.
standardizedCipher
Indicates that an encryption method or cipher conforms to an established, widely accepted standard or specification.
- F. None of above. chosen
Provenance (4 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_69f630d70e3881908adb5ac661569149 |
completed | May 2, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f62d14c24c81909e86678c1b5fd429 |
completed | May 2, 2026, 4:57 p.m. |
Created at: April 27, 2026, 2:12 p.m.