Triple
T10682071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AEAD_CHACHA20_POLY1305 |
E251780
|
entity |
| Predicate | blockFunctionOutputBits |
P4121
|
FINISHED |
| Object | 512 |
—
|
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: 512 | Statement: [AEAD_CHACHA20_POLY1305, blockFunctionOutputBits, 512]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blockFunctionOutputBits Context triple: [AEAD_CHACHA20_POLY1305, blockFunctionOutputBits, 512]
-
A.
bitSlice
Indicates taking a contiguous subset of bits from a larger bit sequence, defined by specified start and end positions.
-
B.
bitWidth
chosen
Indicates the number of bits used to represent or encode a given value, type, or data element.
-
C.
SBoxOutputSize
Indicates the size of the output produced by an S-box transformation in a cryptographic or logical mapping.
-
D.
logicFunction
Indicates a relationship where one entity serves as a logical function or operator that determines the truth value or output based on given inputs or conditions involving another entity.
-
E.
bitLengthFactorization
Indicates a relationship where the bit-length of a number is determined or constrained by the factorization of that number.
- 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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fcc30be481909922844b539b622d |
completed | April 9, 2026, 1:11 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8a93208190a573061387e2aebb |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:10 p.m.