Triple
T18158170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SHA-0 |
E434686
|
entity |
| Predicate | producesDigest |
P91184
|
FINISHED |
| Object | 160-bit message digest |
—
|
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: 160-bit message digest | Statement: [SHA-0, producesDigest, 160-bit message digest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producesDigest Context triple: [SHA-0, producesDigest, 160-bit message digest]
-
A.
hasDigestRepresentation
Indicates that one entity is represented by, or associated with, a condensed or summarized form (a digest) of its content or data.
-
B.
digestSize
chosen
Indicates the size or length of a computed digest (such as a hash or checksum) produced from some data.
-
C.
producesFor
Indicates that one entity creates, manufactures, or generates something specifically intended for another entity’s use, benefit, or distribution.
-
D.
signatureProducer
Indicates that an entity is responsible for creating or generating a particular signature (e.g., cryptographic, digital, or formal).
-
E.
produces
Indicates that one entity creates, generates, or yields another entity as a result or output.
- 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_69d8b90b7a188190b3fc7b8d4a6cd20a |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dec02d9c81909ac6203b7d59c405 |
completed | April 19, 2026, 1:55 p.m. |
| PD | Predicate disambiguation | batch_69e4331baeb88190b21f50a98c36c78e |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:30 a.m.