Triple
T26903548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DEA |
E678090
|
entity |
| Predicate | keyManagementRequirement |
P161317
|
FINISHED |
| Object | shared secret key |
—
|
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: shared secret key | Statement: [DEA, keyManagementRequirement, shared secret key]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyManagementRequirement Context triple: [DEA, keyManagementRequirement, shared secret key]
-
A.
keyManagementType
Indicates the method or scheme by which cryptographic keys are generated, stored, distributed, and controlled within a system or process.
-
B.
supportsKeyManagement
Indicates that one entity provides functionality or capability to handle, store, or control cryptographic keys for another entity or process.
-
C.
supportsKeyManagementProtocol
Indicates that one entity is capable of using or is compatible with a specified key management protocol for handling cryptographic keys.
-
D.
keyUse
Indicates that one entity is used as a key or means of access, control, or identification for another entity.
-
E.
keyMaterial
Indicates that an entity serves as cryptographic key material used to secure, encrypt, or authenticate data in a security-related relationship.
- F. None of above. chosen
Provenance (4 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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61fb127c481908bc480561194a264 |
completed | May 2, 2026, 4 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
| PDg | Predicate description generation | batch_69f6125e54e0819088ee33a20efcc9e6 |
completed | May 2, 2026, 3:03 p.m. |
Created at: April 27, 2026, 5:52 a.m.