Triple
T10157738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AES-CCM |
E233814
|
entity |
| Predicate | nonceLength |
P92328
|
FINISHED |
| Object | 7–13 bytes |
—
|
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: 7–13 bytes | Statement: [AES-CCM, nonceLength, 7–13 bytes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonceLength Context triple: [AES-CCM, nonceLength, 7–13 bytes]
-
A.
variantNonceSize
Indicates that there is a specific or differing size of nonce associated with a given variant in a cryptographic or protocol context.
-
B.
IVLength
Indicates the measured length of an intravenous (IV) line or catheter used in a medical context.
-
C.
recommendedKeyLength
Indicates the suggested or optimal length that a cryptographic key should have for secure use in a given context.
-
D.
usesNonce
Indicates that one entity employs a nonce (a unique, typically one-time-use value) as part of its interaction or operation with another entity.
-
E.
nominalKeySize
Indicates the standard or designated size value associated with a key in a cryptographic or data structure context.
- 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_69ca848e80748190b91d1e04d35512c7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec5507f08190b47f797bacd5640c |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba795808190acc9124c98c6e40f |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4f8f869c8190a82ad040993e0244 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 9:09 p.m.