Triple
T2236380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 6668 |
E49290
|
entity |
| Predicate | title |
P38
|
FINISHED |
| Object |
SHA-2 Data Integrity Verification for the Secure Shell (SSH) Transport Layer Protocol
"SHA-2 Data Integrity Verification for the Secure Shell (SSH) Transport Layer Protocol" is an IETF specification that updates SSH to use SHA-2-based message authentication codes to improve data integrity and security over the transport layer.
|
E248469
|
NE FINISHED |
How this triple was built (4 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: SHA-2 Data Integrity Verification for the Secure Shell (SSH) Transport Layer Protocol | Statement: [RFC 6668, title, SHA-2 Data Integrity Verification for the Secure Shell (SSH) Transport Layer Protocol]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SHA-2 Data Integrity Verification for the Secure Shell (SSH) Transport Layer Protocol Context triple: [RFC 6668, title, SHA-2 Data Integrity Verification for the Secure Shell (SSH) Transport Layer Protocol]
-
A.
The Secure Shell (SSH) Authentication Protocol
The Secure Shell (SSH) Authentication Protocol is a standardized network protocol that defines methods for securely authenticating users and hosts in SSH connections using mechanisms such as passwords, public keys, and keyboard-interactive methods.
-
B.
SSH Communications Security
SSH Communications Security is a Finnish cybersecurity company best known for developing and commercializing the Secure Shell (SSH) protocol and related secure communications solutions.
-
C.
Negotiated Finite Field Diffie-Hellman Ephemeral Parameters for Transport Layer Security (TLS)
"Negotiated Finite Field Diffie-Hellman Ephemeral Parameters for Transport Layer Security (TLS)" is an IETF standard (RFC 7919) that defines secure, standardized finite-field Diffie-Hellman parameter sets for use in TLS to improve cryptographic security and interoperability.
-
D.
Secure Authentication Version 5
Secure Authentication Version 5 is a security enhancement for the DNP3 protocol that provides robust authentication and protection against unauthorized control and cyber attacks in industrial control systems.
-
E.
Curve25519-based schemes
Curve25519-based schemes are cryptographic protocols and algorithms that use the Curve25519 elliptic curve to provide efficient, high-security public-key operations such as key exchange and digital signatures.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: SHA-2 Data Integrity Verification for the Secure Shell (SSH) Transport Layer Protocol Triple: [RFC 6668, title, SHA-2 Data Integrity Verification for the Secure Shell (SSH) Transport Layer Protocol]
Generated description
"SHA-2 Data Integrity Verification for the Secure Shell (SSH) Transport Layer Protocol" is an IETF specification that updates SSH to use SHA-2-based message authentication codes to improve data integrity and security over the transport layer.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: SHA-2 Data Integrity Verification for the Secure Shell (SSH) Transport Layer Protocol Target entity description: "SHA-2 Data Integrity Verification for the Secure Shell (SSH) Transport Layer Protocol" is an IETF specification that updates SSH to use SHA-2-based message authentication codes to improve data integrity and security over the transport layer.
-
A.
The Secure Shell (SSH) Authentication Protocol
The Secure Shell (SSH) Authentication Protocol is a standardized network protocol that defines methods for securely authenticating users and hosts in SSH connections using mechanisms such as passwords, public keys, and keyboard-interactive methods.
-
B.
SSH Communications Security
SSH Communications Security is a Finnish cybersecurity company best known for developing and commercializing the Secure Shell (SSH) protocol and related secure communications solutions.
-
C.
Negotiated Finite Field Diffie-Hellman Ephemeral Parameters for Transport Layer Security (TLS)
"Negotiated Finite Field Diffie-Hellman Ephemeral Parameters for Transport Layer Security (TLS)" is an IETF standard (RFC 7919) that defines secure, standardized finite-field Diffie-Hellman parameter sets for use in TLS to improve cryptographic security and interoperability.
-
D.
Secure Authentication Version 5
Secure Authentication Version 5 is a security enhancement for the DNP3 protocol that provides robust authentication and protection against unauthorized control and cyber attacks in industrial control systems.
-
E.
Curve25519-based schemes
Curve25519-based schemes are cryptographic protocols and algorithms that use the Curve25519 elliptic curve to provide efficient, high-security public-key operations such as key exchange and digital signatures.
- F. None of above. chosen
Provenance (5 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_69a88aa84bdc819086df50e9c20b301e |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc09573848190bf91eddcc2fa0061 |
completed | March 7, 2026, 6:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae6b08c5248190924a28f4c1bd0e2c |
completed | March 9, 2026, 6:39 a.m. |
| NEDg | Description generation | batch_69ae6c5cb33481909261f7010e8e21a6 |
completed | March 9, 2026, 6:44 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69ae6cd61e808190aefca4d4aa1f8e39 |
completed | March 9, 2026, 6:46 a.m. |
Created at: March 4, 2026, 7:47 p.m.