Triple
T30608984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German naval Enigma |
E779124
|
entity |
| Predicate | decryptionCodename |
P169611
|
FINISHED |
| Object | Ultra |
—
|
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: Ultra | Statement: [German naval Enigma, decryptionCodename, Ultra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decryptionCodename Context triple: [German naval Enigma, decryptionCodename, Ultra]
-
A.
coDecipherer
Indicates that two or more entities jointly participated in deciphering or decoding something together.
-
B.
deciphers
Indicates the action of successfully interpreting or figuring out the meaning of something that is difficult to understand or encoded.
-
C.
decryptionRule
Indicates a rule or method used to convert encrypted data back into its original, readable form.
-
D.
securityCodename
Indicates that an entity is assigned a specific codename used for security, confidentiality, or protective identification purposes.
-
E.
codenameLetter
Indicates that one entity is the letter component of another entity’s codename.
- 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_69f224a21fc08190abd9d8dd9eb6bb4c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f689b7bc6c8190b46762f5c16df91a |
completed | May 2, 2026, 11:33 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f0353c88190a05b2db449abe0f4 |
completed | May 2, 2026, 10:47 p.m. |
Created at: April 29, 2026, 8:26 p.m.