Triple
T33027018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BLAKE2s |
E845069
|
entity |
| Predicate | supportsDigestSize |
P91184
|
FINISHED |
| Object | 1–32 bytes |
—
|
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: 1–32 bytes | Statement: [BLAKE2s, supportsDigestSize, 1–32 bytes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDigestSize Context triple: [BLAKE2s, supportsDigestSize, 1–32 bytes]
-
A.
digestSize
chosen
Indicates the size or length of a computed digest (such as a hash or checksum) produced from some data.
-
B.
hasDigestRepresentation
Indicates that one entity is represented by, or associated with, a condensed or summarized form (a digest) of its content or data.
-
C.
digestSizeMax
Indicates the maximum allowable size or length of a digest (e.g., hash or summary) associated with an entity or process.
-
D.
supportsHardwareCryptography
Indicates that one entity provides or enables hardware-based cryptographic operations or capabilities for another entity.
-
E.
supportedBlockSizes
Indicates the specific block sizes that an entity is capable of handling or operating with.
- 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_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:23 a.m.