Triple
T32603766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naor–Reingold pseudorandom function |
E833448
|
entity |
| Predicate | keySizeDependsOn |
P175009
|
FINISHED |
| Object | input length n |
—
|
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: input length n | Statement: [Naor–Reingold pseudorandom function, keySizeDependsOn, input length n]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keySizeDependsOn Context triple: [Naor–Reingold pseudorandom function, keySizeDependsOn, input length n]
-
A.
privateKeySize
Indicates the size or length of a private key used in a cryptographic relationship or operation.
-
B.
keySizeIncrement
Indicates the amount by which a key’s size is increased each time it is expanded or grown.
-
C.
nominalKeySize
Indicates the standard or designated size value associated with a key in a cryptographic or data structure context.
-
D.
consideredInsecureAtKeySize
Indicates that a cryptographic algorithm or mechanism is regarded as insecure when used with a specified key size.
-
E.
supportsKeyLength
Indicates that one entity is capable of handling, accepting, or operating with a specified cryptographic key length associated with another entity.
- F. None of above. chosen
Provenance (4 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_69f3492ab63c8190aec24d5003b47c29 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6cd9bae8c8190b528641499162a75 |
completed | May 3, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cd119cac8190a0b3ebe8b9c742c2 |
completed | May 3, 2026, 4:20 a.m. |
Created at: May 1, 2026, 1:05 a.m.