Triple
T26409167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GHASH |
E663911
|
entity |
| Predicate | inputBlockSize |
P20328
|
FINISHED |
| Object | 128-bit blocks |
—
|
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-bit blocks | Statement: [GHASH, inputBlockSize, 128-bit blocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inputBlockSize Context triple: [GHASH, inputBlockSize, 128-bit blocks]
-
A.
blockSize
chosen
Indicates the size or capacity of a discrete block unit within a larger structure or system.
-
B.
supportedBlockSizes
Indicates the specific block sizes that an entity is capable of handling or operating with.
-
C.
SBoxInputSize
Indicates the size or dimensionality of the input provided to an S-box transformation in a cryptographic context.
-
D.
approximateBlockLength
Indicates that one entity specifies or estimates the length of a block in an approximate or non-exact manner.
-
E.
numberOfBlocks
Indicates the quantity of discrete block units associated with or contained by a given 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f610faa77081908956b6e8b5b1570c |
completed | May 2, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 11:37 p.m.