Triple
T35299624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lorenz cipher |
E1019468
|
entity |
| Predicate | codeNameByAllies |
P90428
|
FINISHED |
| Object | Tunny |
—
|
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: Tunny | Statement: [Lorenz cipher, codeNameByAllies, Tunny]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeNameByAllies Context triple: [Lorenz cipher, codeNameByAllies, Tunny]
-
A.
invasionCodename
Indicates the codename assigned to a specific military invasion operation.
-
B.
nicknamedByAllies
chosen
Indicates that an entity is referred to by a particular nickname specifically given or used by its allies.
-
C.
codenameLetter
Indicates that one entity is the letter component of another entity’s codename.
-
D.
codeNameOfGermanInvasionPlan
Indicates that one entity is the codename assigned to a specific German invasion plan involving the other entity.
-
E.
alliedCodeName
Indicates that one entity is known or referred to by a specific code name within an allied or cooperative context.
- 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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f790206ce081909ead3399bf8d1013 |
completed | May 3, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.