Triple
T35313482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ULTRA |
E1019840
|
entity |
| Predicate | notablyDecrypted |
—
|
GENERATED |
| Object | Enigma-encoded messages |
—
|
UNRECOGNIZED GENERATED |
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablyDecrypted Context triple: [ULTRA, notablyDecrypted, Enigma-encoded messages]
-
A.
notableKey
Indicates that the referenced key is of particular importance or prominence compared to other keys in the same context.
-
B.
notableDeclassification
Indicates that a previously classified item, document, or information has been officially declassified in a way considered historically or publicly significant.
-
C.
notableResistance
Indicates that an entity is recognized for having mounted a significant or distinguished opposition or defense against another entity or force.
-
D.
decryptionAmbiguity
Indicates that the result of a decryption process is not uniquely determined, allowing multiple plausible plaintexts or interpretations from the same encrypted data.
-
E.
notableGate
Indicates that a gate is recognized as significant, prominent, or noteworthy in some context.
- F. None of above. chosen
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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:03 p.m.