Triple
T19351938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spritz |
E484042
|
entity |
| Predicate | cryptographicType |
P135207
|
FINISHED |
| Object | lightweight stream cipher |
—
|
LITERAL 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: lightweight stream cipher | Statement: [Spritz, cryptographicType, lightweight stream cipher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cryptographicType Context triple: [Spritz, cryptographicType, lightweight stream cipher]
-
A.
ciphertextType
Indicates the specific kind or format of ciphertext produced or used in an encryption process.
-
B.
cryptographicModel
Indicates a relationship where one entity serves as, or is based on, a particular cryptographic scheme, framework, or formal model.
-
C.
canBeEncryptedUsing
Indicates that one entity is capable of being transformed into a secure, encoded form by applying the encryption method or key represented by another entity.
-
D.
hasCrypt
Indicates that one entity possesses, contains, or is associated with a crypt belonging to or located within it.
-
E.
cryptographicRelevance
Indicates that something has significance, impact, or utility within a cryptographic context, such as for security, encryption, or cryptographic analysis.
- F. None of above. chosen
Provenance (4 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_69d8e8d244f8819080eb1f3491300db2 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e61905b16881909ab0e932bb9a0cda |
completed | April 20, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69e4dd13a8cc81909cd02668564c9f29 |
completed | April 19, 2026, 1:48 p.m. |
| PDg | Predicate description generation | batch_69e4dde92ff481909006b3f9e8d639d4 |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 1:34 p.m.