Triple
T9931835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curve25519-based schemes |
E192664
|
entity |
| Predicate | typicalPrivateKeySize |
P77466
|
FINISHED |
| Object | 256-bit private scalars with clamping |
—
|
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: 256-bit private scalars with clamping | Statement: [Curve25519-based schemes, typicalPrivateKeySize, 256-bit private scalars with clamping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPrivateKeySize Context triple: [Curve25519-based schemes, typicalPrivateKeySize, 256-bit private scalars with clamping]
-
A.
recommendedKeyLength
Indicates the suggested or optimal length that a cryptographic key should have for secure use in a given context.
-
B.
nominalKeySize
chosen
Indicates the standard or designated size value associated with a key in a cryptographic or data structure context.
-
C.
typicalKey
Indicates that the referenced key is the standard or most commonly used key associated with an entity or 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.
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_69ca82dd978c8190947124ab0d3315ac |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb5b54f348190b8e70e7beff6098a |
completed | April 2, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69cd1d90b8a8819081748f129c0c6ab6 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:43 p.m.