Triple
T26408640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keccak |
E663897
|
entity |
| Predicate | supportsOutputSize |
P165037
|
FINISHED |
| Object | 224 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: 224 bits | Statement: [Keccak, supportsOutputSize, 224 bits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsOutputSize Context triple: [Keccak, supportsOutputSize, 224 bits]
-
A.
hasOutputSize
chosen
Indicates that an entity produces or is associated with an output characterized by a specific size or dimensional measure.
-
B.
supportsOutputType
Indicates that one entity is capable of producing, handling, or generating data or results of the specified output type.
-
C.
supportedBlockSizes
Indicates the specific block sizes that an entity is capable of handling or operating with.
-
D.
hasInputSize
Indicates that an entity is associated with, or requires, a specific size or dimensionality for its input.
-
E.
supportsMediaSize
Indicates that one entity is capable of handling, accommodating, or being compatible with a specified media size.
- 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_69fe920a437081908d5174e8cf7a53a6 |
completed | May 9, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69fe919a9a6c8190acb4483f386e6db7 |
completed | May 9, 2026, 1:44 a.m. |
Created at: April 26, 2026, 11:36 p.m.