Triple
T32498279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Message-Digest Algorithm 5 |
E830584
|
entity |
| Predicate | hashOutputSize |
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: [Message-Digest Algorithm 5, hashOutputSize, 128 bits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hashOutputSize Context triple: [Message-Digest Algorithm 5, hashOutputSize, 128 bits]
-
A.
digestSize
chosen
Indicates the size or length of a computed digest (such as a hash or checksum) produced from some data.
-
B.
hasOutputSize
Indicates that an entity produces or is associated with an output characterized by a specific size or dimensional measure.
-
C.
SBoxOutputSize
Indicates the size of the output produced by an S-box transformation in a cryptographic or logical mapping.
-
D.
digestSizeMax
Indicates the maximum allowable size or length of a digest (e.g., hash or summary) associated with an entity or process.
-
E.
outputLength
Indicates the length or size of the result produced by a process, function, or operation.
- 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: May 1, 2026, 12:59 a.m.