Triple
T33027017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BLAKE2s |
E845069
|
entity |
| Predicate | digestSizeMaxBits |
P175929
|
FINISHED |
| Object | 256 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: 256 bits | Statement: [BLAKE2s, digestSizeMaxBits, 256 bits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: digestSizeMaxBits Context triple: [BLAKE2s, digestSizeMaxBits, 256 bits]
-
A.
digestSizeMax
chosen
Indicates the maximum allowable size or length of a digest (e.g., hash or summary) associated with an entity or process.
-
B.
digestSize
Indicates the size or length of a computed digest (such as a hash or checksum) produced from some data.
-
C.
collisionResistanceBits
Indicates the number of bits of security a cryptographic function provides against finding any two distinct inputs that produce the same output (a collision).
-
D.
MACKeySizeBits
Indicates the size, in bits, of the cryptographic key used for the MAC (Message Authentication Code) operation.
-
E.
signatureSize
Indicates the size or length of a given signature, typically measured in bytes or characters.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:23 a.m.