Triple
T4769005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atbash |
E105879
|
entity |
| Predicate | decryptionMethod |
P14388
|
FINISHED |
| Object | apply same substitution as encryption |
—
|
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: apply same substitution as encryption | Statement: [Atbash, decryptionMethod, apply same substitution as encryption]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decryptionMethod Context triple: [Atbash, decryptionMethod, apply same substitution as encryption]
-
A.
decodingMethod
chosen
Indicates the technique or process used to convert encoded or encrypted data back into its original, interpretable form.
-
B.
coDecipherer
Indicates that two or more entities jointly participated in deciphering or decoding something together.
-
C.
decryptionProcess
Indicates the action or procedure of converting encrypted data back into its original, readable form using the appropriate decryption method or key.
-
D.
decipheredFrom
Indicates that something has been interpreted, decoded, or understood based on information derived from another source.
-
E.
usesEncryptionAlgorithm
Indicates that one entity applies or relies on a specific encryption algorithm to protect data or communications.
- 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6537eb80819096e0ae906c59d605 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6229d8448190a271719e5e30fd82 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:21 p.m.