Triple
T27509746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Playfair cipher |
E694375
|
entity |
| Predicate | decryptionRule |
P162465
|
FINISHED |
| Object | same column letters are replaced by letters above |
—
|
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: same column letters are replaced by letters above | Statement: [Playfair cipher, decryptionRule, same column letters are replaced by letters above]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decryptionRule Context triple: [Playfair cipher, decryptionRule, same column letters are replaced by letters above]
-
A.
decryptionRule
chosen
Indicates a rule or method used to convert encrypted data back into its original, readable form.
-
B.
decryptionRequires
Indicates that performing decryption of some data depends on or needs a specified key, resource, or condition to be fulfilled.
-
C.
deciphers
Indicates the action of successfully interpreting or figuring out the meaning of something that is difficult to understand or encoded.
-
D.
coDecipherer
Indicates that two or more entities jointly participated in deciphering or decoding something together.
-
E.
encryptionRule
Indicates that a specific method or policy is applied to protect data by transforming it into an unreadable form, defining how and under what conditions encryption is performed.
- 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_69ef53842afc8190ba6bd4e4999bda67 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62ef858008190bda723fb47853dce |
completed | May 2, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 1:15 p.m.