Triple
T35299675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tunny cipher |
E1019469
|
entity |
| Predicate | encryptionDevice |
P182706
|
FINISHED |
| Object | Lorenz SZ40 |
—
|
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: Lorenz SZ40 | Statement: [Tunny cipher, encryptionDevice, Lorenz SZ40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encryptionDevice Context triple: [Tunny cipher, encryptionDevice, Lorenz SZ40]
-
A.
supportsHardwareCryptography
Indicates that one entity provides or enables hardware-based cryptographic operations or capabilities for another entity.
-
B.
keyDevice
Indicates that a device functions as a key or primary access/enabling mechanism for another entity or system.
-
C.
encryptionByDefault
Indicates that data is automatically encrypted without requiring any manual configuration or action by the involved parties.
-
D.
cryptUse
Indicates that one entity uses, applies, or relies on a cryptographic method, key, or mechanism in relation to another entity or data.
-
E.
integratedSecureEnclave
Indicates that a system or component includes a built-in secure enclave that isolates and protects sensitive operations or data from the rest of the environment.
- 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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7904a770481908ef3f788e51e8dba |
completed | May 3, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69f78f629d508190b755848162c4e101 |
completed | May 3, 2026, 6:09 p.m. |
Created at: May 3, 2026, 4:03 p.m.