Triple
T13153155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hut 6 |
E312515
|
entity |
| Predicate | usedCryptanalyticMethods |
P22717
|
FINISHED |
| Object | crib-based attacks |
—
|
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: crib-based attacks | Statement: [Hut 6, usedCryptanalyticMethods, crib-based attacks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedCryptanalyticMethods Context triple: [Hut 6, usedCryptanalyticMethods, crib-based attacks]
-
A.
cryptanalysisStatus
Indicates the current state or outcome of efforts to analyze or break a cryptographic system or cipher.
-
B.
cryptographicRelevance
Indicates that something has significance, impact, or utility within a cryptographic context, such as for security, encryption, or cryptographic analysis.
-
C.
canCrackEncryption
Indicates that an entity has the capability to break or bypass the encryption protecting another entity’s data or communications.
-
D.
usesInvestigativeMethods
chosen
Indicates that an entity employs investigative techniques or procedures to gather information, analyze evidence, or uncover facts.
-
E.
usesKeyDependentSBoxes
Indicates that the cryptographic construction employs S-boxes whose behavior or mapping depends on the value of the secret key.
- 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_69d806aabde48190899e13e41659cae5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bbd1d088190b7c69f37fc6eeb64 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:11 p.m.