Triple
T957498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RC4 |
E20655
|
entity |
| Predicate | replacedBy |
P101
|
FINISHED |
| Object | ChaCha20 |
E6785
|
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: ChaCha20 | Statement: [RC4, replacedBy, ChaCha20]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ChaCha20 Context triple: [RC4, replacedBy, ChaCha20]
-
A.
ChaCha20
chosen
ChaCha20 is a modern stream cipher designed by Daniel J. Bernstein, widely used for its high performance and strong security in protocols like TLS.
-
B.
Salsa20
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.
-
C.
Poly1305
Poly1305 is a high-speed message authentication code (MAC) algorithm commonly used with stream ciphers like ChaCha20 to provide data integrity and authenticity.
-
D.
AES-GCM
AES-GCM is an authenticated encryption mode of the Advanced Encryption Standard that provides both data confidentiality and integrity, widely used in modern network and security protocols.
-
E.
AES-CTR
AES-CTR is a widely used symmetric-key encryption mode that turns the AES block cipher into a fast, parallelizable stream cipher by encrypting successive counter values and XORing them with the plaintext.
- 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_69a493b21f2881908132dcf45dcd2f36 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3fac2bc8190a66feb70c68899b2 |
completed | March 1, 2026, 9:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a933b259d08190b03989e2b1575085 |
completed | March 5, 2026, 7:41 a.m. |
Created at: March 1, 2026, 7:40 p.m.