Triple
T35299612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lorenz cipher |
E1019468
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II cryptographic system |
C7649
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: World War II cryptographic system Context triple: [Lorenz cipher, instanceOf, World War II cryptographic system]
-
A.
World War II codebreaker
A World War II codebreaker is a specialist who analyzes and decrypts enemy communications using mathematical, linguistic, and logical techniques to reveal hidden information critical to wartime intelligence and strategy.
-
B.
World War II technology
chosen
World War II technology encompasses the advanced weapons, vehicles, communication systems, and scientific innovations developed and deployed during the conflict, which significantly influenced both the war’s outcome and postwar technological progress.
-
C.
World War II code talkers
World War II code talkers were Indigenous military communicators, most famously Navajo Marines, who used their native languages to create unbreakable tactical codes for secure battlefield transmissions.
-
D.
World War II project
A World War II project is a structured investigation or creative work that explores specific aspects of the Second World War—such as events, people, technology, or impacts—using historical sources to analyze and present findings.
-
E.
U.S. government encryption standard
A U.S. government encryption standard is an officially approved cryptographic algorithm or protocol, such as AES, mandated or recommended by federal authorities to protect sensitive government and public-sector information.
- F. None of above.
Provenance (1 batch)
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. |
Created at: May 3, 2026, 4:03 p.m.