Triple
T7414939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DES |
E171105
|
entity |
| Predicate | effectiveKeySize |
P8686
|
FINISHED |
| Object | 56 bits |
—
|
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: 56 bits | Statement: [DES, effectiveKeySize, 56 bits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectiveKeySize Context triple: [DES, effectiveKeySize, 56 bits]
-
A.
consideredInsecureAtKeySize
Indicates that a cryptographic algorithm or mechanism is regarded as insecure when used with a specified key size.
-
B.
recommendedKeyLength
Indicates the suggested or optimal length that a cryptographic key should have for secure use in a given context.
-
C.
supportsKeyLength
chosen
Indicates that one entity is capable of handling, accepting, or operating with a specified cryptographic key length associated with another entity.
-
D.
initialAuthorizedStrength
Indicates the originally approved or designated level, size, or capacity of a force, group, or resource at the time it was first authorized.
-
E.
supportsVariableKeyLength
Indicates that an entity is capable of operating correctly with cryptographic keys of varying lengths rather than a single fixed key size.
- 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_69c68a618bdc81908d8018edadecd1a4 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2c509ac8190876f207267a33a3b |
completed | March 27, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69c6f0345040819094c5756dfa487faf |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:11 p.m.