Triple
T32542381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naor–Yung encryption paradigm |
E831745
|
entity |
| Predicate | decryptionCondition |
P79867
|
FINISHED |
| Object | decrypt only if the proof verifies |
—
|
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: decrypt only if the proof verifies | Statement: [Naor–Yung encryption paradigm, decryptionCondition, decrypt only if the proof verifies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decryptionCondition Context triple: [Naor–Yung encryption paradigm, decryptionCondition, decrypt only if the proof verifies]
-
A.
decryptionRequires
chosen
Indicates that performing decryption of some data depends on or needs a specified key, resource, or condition to be fulfilled.
-
B.
decryptionRule
Indicates a rule or method used to convert encrypted data back into its original, readable form.
-
C.
decryptionCodename
Indicates that one entity serves as the codename or label used for a particular decryption operation or process involving another entity.
-
D.
authorizationCondition
Indicates the specific rules or requirements that must be satisfied for an action or access to be legally or formally authorized.
-
E.
deciphers
Indicates the action of successfully interpreting or figuring out the meaning of something that is difficult to understand or encoded.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c57fc940819086d7ab256f2cad71 |
completed | May 3, 2026, 3:48 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:02 a.m.