Triple

T2114100
Position Surface form Disambiguated ID Type / Status
Subject Salsa20 E42566 entity
Predicate relatedTo P37 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: [Salsa20, relatedTo, ChaCha20]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ChaCha20
Context triple: [Salsa20, relatedTo, 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. AES-Poly1305
    AES-Poly1305 is an authenticated encryption scheme that pairs the AES block cipher with the Poly1305 message authentication code to provide both confidentiality and integrity.
  • D. Poly1305
    Poly1305 is a high-speed message authentication code (MAC) algorithm commonly used with stream ciphers like ChaCha20 to provide data integrity and authenticity.
  • E. 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.
  • 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_69a8871040f08190aac2e2d0ab6b47ad completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abbb05b51c81908a78c816f492c45c completed March 7, 2026, 5:43 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae30748a7c81908ab3e08b7aa9900a completed March 9, 2026, 2:29 a.m.
Created at: March 4, 2026, 7:43 p.m.