Triple
T34061206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hybrid Public Key Encryption |
E873495
|
entity |
| Predicate | canUseKDF |
P9928
|
FINISHED |
| Object | HKDF-SHA256 |
—
|
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: HKDF-SHA256 | Statement: [Hybrid Public Key Encryption, canUseKDF, HKDF-SHA256]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canUseKDF Context triple: [Hybrid Public Key Encryption, canUseKDF, HKDF-SHA256]
-
A.
canDerive
Indicates that one entity can be logically or procedurally obtained, inferred, or produced from another entity based on defined rules or transformations.
-
B.
canBeEncryptedUsing
Indicates that one entity is capable of being transformed into a secure, encoded form by applying the encryption method or key represented by another entity.
-
C.
canUse
chosen
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
-
D.
hasCryptUse
Indicates that an entity makes use of cryptographic methods, protocols, or mechanisms in its operation or behavior.
-
E.
canUseAuthenticationAlgorithm
Indicates that an entity is able or permitted to employ a specified authentication algorithm for verifying identity or access.
- 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_69f349a4af208190afa14888f9c9fb9d |
completed | April 30, 2026, 12:23 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:52 a.m.