Triple
T33926563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 6668 |
E869766
|
entity |
| Predicate | usesHashFunctionFamily |
P56724
|
FINISHED |
| Object | SHA-2 |
—
|
NE NERFINISHED |
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: SHA-2 | Statement: [RFC 6668, usesHashFunctionFamily, SHA-2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesHashFunctionFamily Context triple: [RFC 6668, usesHashFunctionFamily, SHA-2]
-
A.
hashFamily
Indicates that a hash function belongs to, or is a member of, a particular family of related hash functions.
-
B.
hashFunction
Indicates a relationship where an input value is transformed into a fixed-size output (hash) according to a specific deterministic hashing algorithm.
-
C.
usesKeyDependentSBoxes
Indicates that the cryptographic construction employs S-boxes whose behavior or mapping depends on the value of the secret key.
-
D.
usesHostFamilies
Indicates that one entity relies on or employs host families to provide accommodation, care, or support for another entity.
-
E.
algorithmFamily
chosen
Indicates that one algorithm belongs to, or is categorized under, a broader family or class of related algorithms.
- 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_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:49 a.m.