Triple
T26903517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucifer cipher |
E678089
|
entity |
| Predicate | cryptographicCategory |
P21843
|
FINISHED |
| Object | symmetric block 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: symmetric block cipher | Statement: [Lucifer cipher, cryptographicCategory, symmetric block cipher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cryptographicCategory Context triple: [Lucifer cipher, cryptographicCategory, symmetric block cipher]
-
A.
cryptographicType
Indicates the specific kind or category of cryptographic method, algorithm, or primitive associated with an entity or operation.
-
B.
cryptographicRelevance
Indicates that something has significance, impact, or utility within a cryptographic context, such as for security, encryption, or cryptographic analysis.
-
C.
cryptographicModel
Indicates a relationship where one entity serves as, or is based on, a particular cryptographic scheme, framework, or formal model.
-
D.
cipherCategory
chosen
Indicates that one item is classified as a type or category of cipher to which the other item belongs.
-
E.
hasCrypt
Indicates that one entity possesses, contains, or is associated with a crypt belonging to or located within it.
- F. None of above.
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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61fb127c481908bc480561194a264 |
completed | May 2, 2026, 4 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 5:52 a.m.