Triple
T7414967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DES |
E171105
|
entity |
| Predicate | usesInitialPermutation |
P76807
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [DES, usesInitialPermutation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesInitialPermutation Context triple: [DES, usesInitialPermutation, true]
-
A.
usesInitializationVectorLength
Indicates that an entity employs an initialization vector (IV) of a specified length in a cryptographic or security-related operation.
-
B.
keyExpansion
Indicates the process of deriving a set of subkeys from an original key for use in a cryptographic algorithm.
-
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.
cryptDesigner
Indicates that an entity is the designer or creator responsible for planning or conceiving a particular crypt.
-
E.
usesScrambling
Indicates that one entity applies a scrambling process or technique to another entity or to information associated with it.
- 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_69c68a618bdc81908d8018edadecd1a4 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2c509ac8190876f207267a33a3b |
completed | March 27, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69c6f0345040819094c5756dfa487faf |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f1c3307481909a7f6bb69d4fddac |
completed | March 27, 2026, 9:08 p.m. |
Created at: March 27, 2026, 3:11 p.m.