Triple
T9931335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MD5 |
E192654
|
entity |
| Predicate | digestSize |
P91184
|
FINISHED |
| Object | 128 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: 128 bits | Statement: [MD5, digestSize, 128 bits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: digestSize Context triple: [MD5, digestSize, 128 bits]
-
A.
nominalKeySize
Indicates the standard or designated size value associated with a key in a cryptographic or data structure context.
-
B.
SBoxOutputSize
Indicates the size of the output produced by an S-box transformation in a cryptographic or logical mapping.
-
C.
blockSize
Indicates the size or capacity of a discrete block unit within a larger structure or system.
-
D.
variantNonceSize
Indicates that there is a specific or differing size of nonce associated with a given variant in a cryptographic or protocol context.
-
E.
stateSizeBytes
Indicates the size of a given state or stateful data in terms of the number of bytes it occupies.
- 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_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. |
| PDg | Predicate description generation | batch_69cd3581a9688190a00cef4c3eebb0ae |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:43 p.m.