Triple
T37123853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HChaCha20 |
E919336
|
entity |
| Predicate | inputKeySize |
P77466
|
FINISHED |
| Object | 256-bit 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: 256-bit key | Statement: [HChaCha20, inputKeySize, 256-bit key]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inputKeySize Context triple: [HChaCha20, inputKeySize, 256-bit key]
-
A.
privateKeySize
Indicates the size or length of a private key used in a cryptographic relationship or operation.
-
B.
keySizeDependsOn
Indicates that the size or length of a key is determined or constrained by another parameter, condition, or entity.
-
C.
nominalKeySize
chosen
Indicates the standard or designated size value associated with a key in a cryptographic or data structure context.
-
D.
keySizeIncrement
Indicates the amount by which a key’s size is increased each time it is expanded or grown.
-
E.
supportsKeyLength
Indicates that one entity is capable of handling, accepting, or operating with a specified cryptographic key length associated with another entity.
- 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_69f76e9d13e48190a108f7fbf80ff375 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:15 p.m.