Triple
T26408361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PRESENT |
E663891
|
entity |
| Predicate | usesPermutationLayer |
P166148
|
FINISHED |
| Object | bitwise permutation |
—
|
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: bitwise permutation | Statement: [PRESENT, usesPermutationLayer, bitwise permutation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPermutationLayer Context triple: [PRESENT, usesPermutationLayer, bitwise permutation]
-
A.
usesFinalPermutation
Indicates that an entity applies or relies on a final permutation step (typically a last reordering or transformation) within a process or algorithm.
-
B.
usesInitialPermutation
Indicates that an operation or process applies an initial permutation step to its input elements before performing further actions.
-
C.
usesKeyDependentSBoxes
Indicates that the cryptographic construction employs S-boxes whose behavior or mapping depends on the value of the secret key.
-
D.
hasPermutationRank
Indicates that one entity is assigned a specific ordinal position within the set of all permutations of another entity.
-
E.
usesSBoxes
Indicates that one entity employs substitution boxes (S-boxes) as part of its operation or implementation.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f66003a3f48190a2ba6da5aafbb5cb |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 26, 2026, 11:36 p.m.