Triple
T7414815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rijndael |
E171102
|
entity |
| Predicate | AESBlockSize |
P20328
|
FINISHED |
| Object | 128 bits |
—
|
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: 128 bits | Statement: [Rijndael, AESBlockSize, 128 bits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AESBlockSize Context triple: [Rijndael, AESBlockSize, 128 bits]
-
A.
blockSize
chosen
Indicates the size or capacity of a discrete block unit within a larger structure or system.
-
B.
approximateBlockLength
Indicates that one entity specifies or estimates the length of a block in an approximate or non-exact manner.
-
C.
consideredInsecureAtKeySize
Indicates that a cryptographic algorithm or mechanism is regarded as insecure when used with a specified key size.
-
D.
supportedBlockSizes
Indicates the specific block sizes that an entity is capable of handling or operating with.
-
E.
ciphertextExpansion
Indicates that applying the encryption process to the input increases its length, specifying how much the ciphertext expands relative to the original 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_69c68a618bdc81908d8018edadecd1a4 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2c509ac8190876f207267a33a3b |
completed | March 27, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69c6f0345040819094c5756dfa487faf |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:11 p.m.