Triple
T10532254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SHA-256 |
E248473
|
entity |
| Predicate | hasDigestSize |
P91184
|
FINISHED |
| Object | 256 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: 256 bits | Statement: [SHA-256, hasDigestSize, 256 bits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDigestSize Context triple: [SHA-256, hasDigestSize, 256 bits]
-
A.
digestSize
chosen
Indicates the size or length of a computed digest (such as a hash or checksum) produced from some data.
-
B.
hasDigestRepresentation
Indicates that one entity is represented by, or associated with, a condensed or summarized form (a digest) of its content or data.
-
C.
signatureSize
Indicates the size or length of a given signature, typically measured in bytes or characters.
-
D.
SBoxOutputSize
Indicates the size of the output produced by an S-box transformation in a cryptographic or logical mapping.
-
E.
hasSize
Indicates that one entity possesses a particular physical magnitude or extent, such as length, volume, or overall dimensions.
- 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d50a17f23081909f3372e160e21670 |
completed | April 7, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69d4fb9729288190a0149f127acd7ae3 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:30 p.m.