Triple
T33057336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grain-128 |
E845876
|
entity |
| Predicate | usesKeyAndIV |
P84158
|
FINISHED |
| Object | secret key |
—
|
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: secret key | Statement: [Grain-128, usesKeyAndIV, secret key]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesKeyAndIV Context triple: [Grain-128, usesKeyAndIV, secret key]
-
A.
usesInitializationVectorLength
Indicates that an entity employs an initialization vector (IV) of a specified length in a cryptographic or security-related operation.
-
B.
supportsKeyWhitening
Indicates that one entity provides or enables key whitening functionality for another entity or cryptographic process.
-
C.
usesKeyScheduleLike
Indicates that one cryptographic algorithm employs a key schedule that is the same as, or closely derived from, the key schedule of another algorithm.
-
D.
usesEncryptionAlgorithm
Indicates that one entity applies or relies on a specific encryption algorithm to protect data or communications.
-
E.
cryptUse
chosen
Indicates that one entity uses, applies, or relies on a cryptographic method, key, or mechanism in relation to another entity or data.
- 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_69f3495333b8819095e9af56855b9061 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:25 a.m.