Triple
T17051280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | oblivious RAM |
E413702
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | data-oblivious algorithmic primitive |
C3162
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: data-oblivious algorithmic primitive Context triple: [oblivious RAM, instanceOf, data-oblivious algorithmic primitive]
-
A.
cryptographic primitive
chosen
A cryptographic primitive is a low-level, well-defined algorithm or protocol (such as a hash function, block cipher, or digital signature scheme) that serves as a basic building block for constructing more complex cryptographic systems and protocols.
-
B.
cryptographic data structure
A cryptographic data structure is a data organization that uses cryptographic primitives to ensure properties like integrity, authenticity, privacy, or verifiability of the stored or processed information.
-
C.
end-to-end auditable voting scheme
An end-to-end auditable voting scheme is a voting system that allows each voter and independent observers to verify, from ballot casting through tallying, that all recorded votes are correctly included in the final result without revealing how any individual voted.
-
D.
cryptanalytic device
A cryptanalytic device is a tool or machine designed to analyze and break cryptographic systems by discovering hidden keys, patterns, or vulnerabilities in encrypted data.
-
E.
cryptographic protocol framework
A cryptographic protocol framework is a structured set of tools, abstractions, and rules that enables the design, specification, analysis, and implementation of secure communication protocols.
- F. None of above.
Provenance (1 batch)
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_69d886cde3d481908d4d01ba88ba7eb7 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:34 a.m.