Triple

T338766
Position Surface form Disambiguated ID Type / Status
Subject ChaCha20 E6785 entity
Predicate comparedWith P278 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: [ChaCha20, comparedWith, Salsa20]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Salsa20
Context triple: [ChaCha20, comparedWith, 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. 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. RC4 stream cipher
    The RC4 stream cipher is a once-widely used symmetric key algorithm known for its simplicity and speed in software, but now considered insecure due to multiple discovered vulnerabilities.
  • 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_69a2e79434908190a9d5afe415153ad9 completed Feb. 28, 2026, 1:03 p.m.
NER Named-entity recognition batch_69a2eae3a27c81909fc7deb600125fb1 completed Feb. 28, 2026, 1:17 p.m.
NED1 Entity disambiguation (via context triple) batch_69a3e572e9c48190b177b363ed8a8404 completed March 1, 2026, 7:06 a.m.
Created at: Feb. 28, 2026, 1:08 p.m.