Triple
T7934632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ElGamal |
E184257
|
entity |
| Predicate | randomness |
P29140
|
FINISHED |
| Object | uses fresh random exponent for each 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: uses fresh random exponent for each encryption | Statement: [ElGamal, randomness, uses fresh random exponent for each encryption]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: randomness Context triple: [ElGamal, randomness, uses fresh random exponent for each encryption]
-
A.
stochastic
chosen
Indicates that the relationship or process involves randomness or probabilistic behavior rather than being fully deterministic.
-
B.
canBeRandomized
Indicates that the entity is capable of having its state, order, or selection determined by a random process.
-
C.
rarity
Indicates how uncommon or infrequently an entity or event occurs relative to others in a given context.
-
D.
defaultRNGType
Indicates the standard or primary random number generator type that should be used when no specific RNG type is explicitly chosen.
-
E.
generation
Indicates the relationship in which one entity produces, creates, or brings another entity into existence.
- 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_69ca8290c21c8190906a5ca6fe2b03c4 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3aeb132c8190bea4906aaf51b869 |
completed | March 31, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69cae9335f288190ba96781fd6576a2b |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:08 p.m.