Triple
T32515941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NIST P-256 family |
E831061
|
entity |
| Predicate | publicKeySizeApprox |
P6061
|
FINISHED |
| Object | 512 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: 512 bits | Statement: [NIST P-256 family, publicKeySizeApprox, 512 bits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicKeySizeApprox Context triple: [NIST P-256 family, publicKeySizeApprox, 512 bits]
-
A.
privateKeySize
Indicates the size or length of a private key used in a cryptographic relationship or operation.
-
B.
nominalKeySize
Indicates the standard or designated size value associated with a key in a cryptographic or data structure context.
-
C.
keySizeDependsOn
Indicates that the size or length of a key is determined or constrained by another parameter, condition, or entity.
-
D.
approximateSize
chosen
Indicates that one entity has a size that is roughly or approximately equal to the size of another entity.
-
E.
signatureSize
Indicates the size or length of a given signature, typically measured in bytes or characters.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fec8aef1d8819094c7fd7074038e6b |
completed | May 9, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69fec639876481908efd84a3631a4271 |
completed | May 9, 2026, 5:29 a.m. |
Created at: May 1, 2026, 1 a.m.