Triple
T32498155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Secure Hash Standard |
E830581
|
entity |
| Predicate | definesOutput |
P77812
|
FINISHED |
| Object | fixed-size cryptographic hash values |
—
|
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: fixed-size cryptographic hash values | Statement: [Secure Hash Standard, definesOutput, fixed-size cryptographic hash values]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesOutput Context triple: [Secure Hash Standard, definesOutput, fixed-size cryptographic hash values]
-
A.
outputsTo
Indicates that the result or data produced by one entity is directed or sent to another entity as its destination or target.
-
B.
outputIs
Indicates that one entity functions as the result, product, or outcome produced by another entity or process.
-
C.
outputOf
Indicates that one entity is the result or product generated by the processing, operation, or behavior of another entity.
-
D.
outputProperty
chosen
Indicates that a property or attribute is produced, exposed, or yielded as the output of a process, function, or system.
-
E.
outputSpecifier
Indicates how the result or outcome of an action, process, or computation is to be formatted, structured, or delivered.
- 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_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
Created at: May 1, 2026, 12:59 a.m.