Triple
T2236406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 6668 |
E49290
|
entity |
| Predicate | cryptographicPrimitive |
P21840
|
FINISHED |
| Object | SHA-2 family |
—
|
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: SHA-2 family | Statement: [RFC 6668, cryptographicPrimitive, SHA-2 family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cryptographicPrimitive Context triple: [RFC 6668, cryptographicPrimitive, SHA-2 family]
-
A.
cryptographicModel
Indicates a relationship where one entity serves as, or is based on, a particular cryptographic scheme, framework, or formal model.
-
B.
hasCrypt
Indicates that one entity possesses, contains, or is associated with a crypt belonging to or located within it.
-
C.
algorithmType
chosen
Indicates the specific kind or category of algorithm associated with an entity or process.
-
D.
cipherCategory
Indicates that one item is classified as a type or category of cipher to which the other item belongs.
-
E.
usesEncryptionAlgorithm
Indicates that one entity applies or relies on a specific encryption algorithm to protect data or communications.
- 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_69a88aa84bdc819086df50e9c20b301e |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc09573848190bf91eddcc2fa0061 |
completed | March 7, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69abbdafc07881909101266a33ae7031 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.