Triple
T2114116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salsa20 |
E42566
|
entity |
| Predicate | updateFunction |
P23285
|
FINISHED |
| Object | quarter-round function |
—
|
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: quarter-round function | Statement: [Salsa20, updateFunction, quarter-round function]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: updateFunction Context triple: [Salsa20, updateFunction, quarter-round function]
-
A.
functionChange
Indicates that an entity’s function, role, or operational behavior has been altered from one state or purpose to another.
-
B.
updateProcess
Indicates the action or procedure by which an existing item, system, or state is modified to a newer or revised version.
-
C.
updated
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or status.
-
D.
associatedFunction
chosen
Indicates that one entity has a related or linked function that is conceptually or operationally connected to it.
-
E.
affectedFunction
Indicates that one entity has an impact on, alters, or impairs the operation or behavior of another entity’s function.
- 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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb05b51c81908a78c816f492c45c |
completed | March 7, 2026, 5:43 a.m. |
| PD | Predicate disambiguation | batch_69abb7ba08948190a3c236bb53ee4257 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.