Triple
T5479573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GSM |
E123436
|
entity |
| Predicate | keyGenerationAlgorithm |
P21840
|
FINISHED |
| Object | A8 |
—
|
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: A8 | Statement: [GSM, keyGenerationAlgorithm, A8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyGenerationAlgorithm Context triple: [GSM, keyGenerationAlgorithm, A8]
-
A.
keyGenerationStep
Indicates a specific stage or phase within a multi-step process of generating a cryptographic or security-related key.
-
B.
keyDerivation
Indicates that one cryptographic key is generated or derived from another key or base secret using a specific derivation process.
-
C.
securityGeneration
Indicates the creation or issuance of a security (such as a financial instrument or credential) as a result of some process or action.
-
D.
algorithmType
chosen
Indicates the specific kind or category of algorithm associated with an entity or process.
-
E.
keyAgreement
Indicates that two or more parties participate in a cryptographic process to establish a shared secret key for secure communication.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9248ca348190aa116cace0f9b07a |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd91a58c448190904964a439045e05 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.