Triple
T33926602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIPS 180-4 |
E869767
|
entity |
| Predicate | hashOutputLengthBits |
P91184
|
FINISHED |
| Object | 160 |
—
|
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 | Statement: [FIPS 180-4, hashOutputLengthBits, 160]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hashOutputLengthBits Context triple: [FIPS 180-4, hashOutputLengthBits, 160]
-
A.
outputLength
Indicates the length or size of the result produced by a process, function, or operation.
-
B.
digestSize
chosen
Indicates the size or length of a computed digest (such as a hash or checksum) produced from some data.
-
C.
SBoxOutputSize
Indicates the size of the output produced by an S-box transformation in a cryptographic or logical mapping.
-
D.
collisionResistanceBits
Indicates the number of bits of security a cryptographic function provides against finding any two distinct inputs that produce the same output (a collision).
-
E.
scriptPubKeyHashLength
Indicates the length of the hash value used in the scriptPubKey field of a transaction 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_69f349992c508190aa4afa24a086cc8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
Created at: May 1, 2026, 1:49 a.m.