Triple

T19494433
Position Surface form Disambiguated ID Type / Status
Subject Feistel network E487732 entity
Predicate usedBy P260 FINISHED
Object Twofish NE NERFINISHED

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: Twofish | Statement: [Feistel network, usedBy, Twofish]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Twofish
Context triple: [Feistel network, usedBy, Twofish]
  • A. Twofish chosen
    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).
  • B. 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).
  • C. 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.
  • D. 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.
  • E. RC5
    RC5 is a symmetric-key block cipher designed by cryptographer Ronald L. Rivest, known for its simplicity, parameter flexibility, and use in various encryption applications.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e8d9d1c88190b01cd78b8be49384 completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e6349002788190afe7831d008d440f completed April 20, 2026, 2:13 p.m.
Created at: April 10, 2026, 1:40 p.m.