Triple
T37123891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HChaCha20 |
E919336
|
entity |
| Predicate | subkeyUsage |
P157756
|
FINISHED |
| Object | used as key for subsequent ChaCha20 encryption |
—
|
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: used as key for subsequent ChaCha20 encryption | Statement: [HChaCha20, subkeyUsage, used as key for subsequent ChaCha20 encryption]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subkeyUsage Context triple: [HChaCha20, subkeyUsage, used as key for subsequent ChaCha20 encryption]
-
A.
keyUse
Indicates that one entity is used as a key or means of access, control, or identification for another entity.
-
B.
keyUsageContext
chosen
Indicates the specific circumstances, purposes, or operational conditions under which a key is intended or permitted to be used.
-
C.
keySubsidiary
Indicates that one organization is the primary or most important subsidiary within a group of related companies.
-
D.
keyStatus
Indicates the current state or condition of a key (e.g., whether it is active, valid, revoked, or expired) in relation to its use or authorization.
-
E.
keyIntermediate
Indicates that something serves as an essential transitional or intermediary step, component, or stage within a larger process or relationship.
- 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_69f76e9d13e48190a108f7fbf80ff375 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:15 p.m.