Triple
T11033200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Secure Shell (SSH) Protocol Assigned Numbers |
E260809
|
entity |
| Predicate | references |
P771
|
FINISHED |
| Object |
The Secure Shell (SSH) Connection Protocol
The Secure Shell (SSH) Connection Protocol is a core component of SSH that multiplexes multiple logical channels over a single encrypted transport, enabling secure interactive sessions, port forwarding, and other services between networked hosts.
|
E904946
|
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: The Secure Shell (SSH) Connection Protocol | Statement: [The Secure Shell (SSH) Protocol Assigned Numbers, references, The Secure Shell (SSH) Connection Protocol]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: The Secure Shell (SSH) Connection Protocol Context triple: [The Secure Shell (SSH) Protocol Assigned Numbers, references, The Secure Shell (SSH) Connection Protocol]
-
A.
The Secure Shell (SSH) Transport Layer Protocol
The Secure Shell (SSH) Transport Layer Protocol is the core low-level component of SSH that provides secure, encrypted, and integrity-protected communication over an insecure network, forming the foundation for higher-level SSH services.
-
B.
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.
-
C.
The Secure Shell (SSH) Protocol Assigned Numbers
"The Secure Shell (SSH) Protocol Assigned Numbers" is an IETF RFC that catalogs and standardizes the numeric identifiers and registries used by the SSH protocol for its various message types, algorithms, and parameters.
-
D.
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.
-
E.
PPP over Secure Shell (SSH)
PPP over Secure Shell (SSH) is an IETF-defined method for encapsulating the Point-to-Point Protocol within SSH sessions to provide secure, encrypted tunneling for network traffic.
- 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: The Secure Shell (SSH) Connection Protocol Triple: [The Secure Shell (SSH) Protocol Assigned Numbers, references, The Secure Shell (SSH) Connection Protocol]
Generated description
The Secure Shell (SSH) Connection Protocol is a core component of SSH that multiplexes multiple logical channels over a single encrypted transport, enabling secure interactive sessions, port forwarding, and other services between networked hosts.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: The Secure Shell (SSH) Connection Protocol Target entity description: The Secure Shell (SSH) Connection Protocol is a core component of SSH that multiplexes multiple logical channels over a single encrypted transport, enabling secure interactive sessions, port forwarding, and other services between networked hosts.
-
A.
The Secure Shell (SSH) Transport Layer Protocol
The Secure Shell (SSH) Transport Layer Protocol is the core low-level component of SSH that provides secure, encrypted, and integrity-protected communication over an insecure network, forming the foundation for higher-level SSH services.
-
B.
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.
-
C.
The Secure Shell (SSH) Protocol Assigned Numbers
"The Secure Shell (SSH) Protocol Assigned Numbers" is an IETF RFC that catalogs and standardizes the numeric identifiers and registries used by the SSH protocol for its various message types, algorithms, and parameters.
-
D.
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.
-
E.
PPP over Secure Shell (SSH)
PPP over Secure Shell (SSH) is an IETF-defined method for encapsulating the Point-to-Point Protocol within SSH sessions to provide secure, encrypted tunneling for network traffic.
- 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797e650b48190967c53f54e3464ad |
completed | April 9, 2026, 12:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e3e72b5e3881908e7230c03dc35f85 |
completed | April 18, 2026, 8:18 p.m. |
| NEDg | Description generation | batch_69e3f01f9d048190b553184f0f6ce29c |
completed | April 18, 2026, 8:57 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69e3f3fef9308190b0354ed436c32e4c |
completed | April 18, 2026, 9:13 p.m. |
Created at: April 8, 2026, 9:25 p.m.