Triple
T9932124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ed448 |
E192670
|
entity |
| Predicate | hashFunctionUsed |
P8884
|
FINISHED |
| Object | SHAKE256 |
—
|
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: SHAKE256 | Statement: [Ed448, hashFunctionUsed, SHAKE256]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hashFunctionUsed Context triple: [Ed448, hashFunctionUsed, SHAKE256]
-
A.
hashFunction
chosen
Indicates a relationship where an input value is transformed into a fixed-size output (hash) according to a specific deterministic hashing algorithm.
-
B.
hasKeyFunction
Indicates that one entity serves as a primary or essential function or role for another entity.
-
C.
cryptFunction
Indicates a function or method that performs cryptographic processing, such as encrypting, decrypting, or otherwise transforming data using a cryptographic algorithm.
-
D.
usesFinalPermutation
Indicates that an entity applies or relies on a final permutation step (typically a last reordering or transformation) within a process or algorithm.
-
E.
hasPartitionFunction
Indicates that an entity is associated with a specific partition function that characterizes its statistical or thermodynamic behavior.
- 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_69ca82dd978c8190947124ab0d3315ac |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb5b54f348190b8e70e7beff6098a |
completed | April 2, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9428cc81909b4b4938566d78a7 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:43 p.m.