Triple
T18158215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SHA-2 |
E434687
|
entity |
| Predicate | hashLengthRangeBits |
P54172
|
FINISHED |
| Object | 224–512 |
—
|
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: 224–512 | Statement: [SHA-2, hashLengthRangeBits, 224–512]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hashLengthRangeBits Context triple: [SHA-2, hashLengthRangeBits, 224–512]
-
A.
hasLengthRange
chosen
Indicates that an entity’s length falls within a specified minimum-to-maximum range.
-
B.
hasBodyLengthRange
Indicates the range of possible body lengths associated with an entity, typically expressed as a minimum and maximum value.
-
C.
bitWidth
Indicates the number of bits used to represent or encode a given value, type, or data element.
-
D.
approximateBlockLength
Indicates that one entity specifies or estimates the length of a block in an approximate or non-exact manner.
-
E.
bitLengthFactorization
Indicates a relationship where the bit-length of a number is determined or constrained by the factorization of that number.
- 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.