Triple
T5768313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ZRTP |
E127265
|
entity |
| Predicate | supportsCipher |
P32016
|
FINISHED |
| Object | Twofish |
E299185
|
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: Twofish | Statement: [ZRTP, supportsCipher, Twofish]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Twofish Context triple: [ZRTP, supportsCipher, 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.
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.
-
D.
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.
-
E.
Advanced Encryption Standard
Advanced Encryption Standard is a widely used symmetric block cipher standard that secures digital data in applications ranging from wireless networks to government communications.
- 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_69c00834f6308190851b0abeddd8ed7e |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0335f23c081909b35020801e3ef12 |
completed | March 22, 2026, 6:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c07e61127c8190833e279403af6605 |
completed | March 22, 2026, 11:42 p.m. |
Created at: March 22, 2026, 3:49 p.m.