Triple
T32550827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P-521 |
E831967
|
entity |
| Predicate | approximateSecurity |
P2981
|
FINISHED |
| Object | 256-bit classical security |
—
|
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 classical security | Statement: [P-521, approximateSecurity, 256-bit classical security]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateSecurity Context triple: [P-521, approximateSecurity, 256-bit classical security]
-
A.
typicalSecurityLevel
Indicates the usual or standard security level that is generally applied or expected in a given context or system.
-
B.
estimatedStrength
chosen
Indicates that a value represents an approximate or inferred level, magnitude, or intensity of something rather than a precisely measured strength.
-
C.
suitableForGeneralSecurityUse
Indicates that something is appropriate and reliable for use in broad, non-specialized security applications or contexts.
-
D.
securityGuarantee
Indicates a commitment by one party to protect or defend another party against specified threats or risks.
-
E.
canSecure
Indicates that one entity has the ability or capacity to protect, safeguard, or make another entity safe from harm, loss, or unauthorized access.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69feb342994081909481ec8ec5d44928 |
completed | May 9, 2026, 4:08 a.m. |
| PD | Predicate disambiguation | batch_69feb046e4e48190b96649aa28529cc9 |
completed | May 9, 2026, 3:55 a.m. |
Created at: May 1, 2026, 1:02 a.m.