Triple
T28397108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TLS DHE ciphersuites |
E719310
|
entity |
| Predicate | keyExchangeGroupType |
P21838
|
FINISHED |
| Object | finite-field Diffie–Hellman group |
—
|
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: finite-field Diffie–Hellman group | Statement: [TLS DHE ciphersuites, keyExchangeGroupType, finite-field Diffie–Hellman group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyExchangeGroupType Context triple: [TLS DHE ciphersuites, keyExchangeGroupType, finite-field Diffie–Hellman group]
-
A.
keyAgreement
Indicates that two or more parties participate in a cryptographic process to establish a shared secret key for secure communication.
-
B.
keyType
chosen
Indicates the classification or category of a key in relation to how it is used or defined within a system or context.
-
C.
keyManagementType
Indicates the method or scheme by which cryptographic keys are generated, stored, distributed, and controlled within a system or process.
-
D.
cipherSuiteIdentifier
Indicates the specific cryptographic cipher suite used or referenced in a communication or security context.
-
E.
isKeyInterchangeFor
Indicates that one location or facility serves as a primary transfer point connecting major routes, lines, or modes of transport for another.
- 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_69eff6efd1b08190ae3cefd4f11388a2 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64cf0b6a08190b8c7860469c7b000 |
completed | May 2, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 1:17 a.m.