Triple
T9311888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ChaCha |
E224025
|
entity |
| Predicate | basedOn |
P98
|
FINISHED |
| Object | Salsa20 |
E42566
|
NE 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: Salsa20 | Statement: [ChaCha, basedOn, Salsa20]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Salsa20 Context triple: [ChaCha, basedOn, Salsa20]
-
A.
Salsa20
chosen
Salsa20 is a high-speed stream cipher designed by Daniel J. Bernstein, widely used in modern cryptography for its strong security and efficient software performance.
-
B.
ChaCha20
ChaCha20 is a modern stream cipher designed by Daniel J. Bernstein, widely used for its high performance and strong security in protocols like TLS.
-
C.
Twofish
Twofish is a symmetric key block cipher known for its speed, flexibility, and strong security, and was a finalist in the competition to become the Advanced Encryption Standard (AES).
-
D.
Serpent cipher
Serpent cipher is a symmetric-key block cipher and former AES finalist known for its strong security margin and conservative design based on a substitution–permutation network structure.
-
E.
Rijndael
Rijndael is a symmetric block cipher designed by Joan Daemen and Vincent Rijmen that was selected by NIST as the basis for the Advanced Encryption Standard (AES).
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca8425f4fc81909c1c586e9a5b7530 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd20ae96e481909a1af9ea1c91f2b2 |
completed | April 1, 2026, 1:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d0c797640c8190be003e321faf3b86 |
completed | April 4, 2026, 8:11 a.m. |
Created at: March 30, 2026, 7:37 p.m.