Triple
T33027019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BLAKE2s |
E845069
|
entity |
| Predicate | supportsKeyedHashing |
P206320
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [BLAKE2s, supportsKeyedHashing, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsKeyedHashing Context triple: [BLAKE2s, supportsKeyedHashing, true]
-
A.
requiresHashableElements
Indicates that the relationship or operation can only be applied when all involved elements support hashing (i.e., can be used as keys in hash-based structures).
-
B.
supportsMultipleKeys
Indicates that an entity is capable of handling, accepting, or operating with more than one key simultaneously or in parallel.
-
C.
supportsVariableKeyLength
Indicates that an entity is capable of operating correctly with cryptographic keys of varying lengths rather than a single fixed key size.
-
D.
supportsKeyStorage
Indicates that an entity is capable of securely storing cryptographic keys or similar sensitive key material.
-
E.
supportsPrecomputedKeySchedule
Indicates that an entity is capable of using or handling a cryptographic key schedule that has been computed in advance rather than generating it on the fly.
- F. None of above. chosen
Provenance (4 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_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:23 a.m.