Triple
T14877506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zodiac Killer |
E349904
|
entity |
| Predicate | cipherStatus |
P11577
|
FINISHED |
| Object | some ciphers solved, some unsolved |
—
|
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: some ciphers solved, some unsolved | Statement: [Zodiac Killer, cipherStatus, some ciphers solved, some unsolved]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cipherStatus Context triple: [Zodiac Killer, cipherStatus, some ciphers solved, some unsolved]
-
A.
cipherKey
Indicates that one entity serves as the cryptographic key used to encrypt or decrypt information associated with another entity.
-
B.
cipherCategory
Indicates that one item is classified as a type or category of cipher to which the other item belongs.
-
C.
cryptanalysisStatus
chosen
Indicates the current state or outcome of efforts to analyze or break a cryptographic system or cipher.
-
D.
cryptUse
Indicates that one entity uses, applies, or relies on a cryptographic method, key, or mechanism in relation to another entity or data.
-
E.
encryptionDirection
Indicates the direction in which data is being encrypted, specifying whether it is going from source to destination or vice versa.
- 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_69d822ee4f408190b6ac3b2fa434f0df |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded5e4e4448190a8796573bc6d1069 |
completed | April 15, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69de8c1a2bcc81908f914e2e2ced65eb |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:55 a.m.