Triple
T32498527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PSS (Probabilistic Signature Scheme) |
E830589
|
entity |
| Predicate | securityProvedIn |
P127292
|
FINISHED |
| Object | random oracle model |
—
|
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: random oracle model | Statement: [PSS (Probabilistic Signature Scheme), securityProvedIn, random oracle model]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: securityProvedIn Context triple: [PSS (Probabilistic Signature Scheme), securityProvedIn, random oracle model]
-
A.
securityProof
chosen
Indicates that there exists a formal argument or evidence demonstrating that a system, protocol, or mechanism satisfies specified security properties under defined assumptions.
-
B.
securityGuarantee
Indicates a commitment by one party to protect or defend another party against specified threats or risks.
-
C.
securedAgainst
Indicates that one entity is protected or safeguarded against threats, risks, or harmful actions originating from another entity or source.
-
D.
securityPillar
Indicates that one entity functions as a foundational security pillar or core security domain in relation to another entity.
-
E.
securityOutcome
Indicates the result or consequence of a security-related event, measure, or decision for the involved entities.
- 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7bbf906d8819099020e548dd56bc9 |
completed | May 3, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a2dcf88190a7c9e109e41267be |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 1, 2026, 12:59 a.m.