Triple
T26408330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S-box |
E663890
|
entity |
| Predicate | usedInCipher |
P76797
|
FINISHED |
| Object | Data Encryption Standard |
—
|
NE NERFINISHED |
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: Data Encryption Standard | Statement: [S-box, usedInCipher, Data Encryption Standard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInCipher Context triple: [S-box, usedInCipher, Data Encryption Standard]
-
A.
usesSBoxes
Indicates that one entity employs substitution boxes (S-boxes) as part of its operation or implementation.
-
B.
cryptUse
Indicates that one entity uses, applies, or relies on a cryptographic method, key, or mechanism in relation to another entity or data.
-
C.
usesKeyDependentSBoxes
Indicates that the cryptographic construction employs S-boxes whose behavior or mapping depends on the value of the secret key.
-
D.
usesEncryptionAlgorithm
Indicates that one entity applies or relies on a specific encryption algorithm to protect data or communications.
-
E.
usesSBox
chosen
Indicates that one entity employs or applies an S-box (substitution box) as part of its operation or 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 26, 2026, 11:36 p.m.