Triple
T287016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4251 |
E5905
|
entity |
| Predicate | protocol |
P1992
|
FINISHED |
| Object | Secure Shell |
E1267
|
NE 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: Secure Shell | Statement: [RFC 4251, protocol, Secure Shell]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Secure Shell Context triple: [RFC 4251, protocol, Secure Shell]
-
A.
SSH
chosen
SSH (Secure Shell) is a cryptographic network protocol used to securely access, manage, and transfer data between remote computers over unsecured networks.
-
B.
SSL
SSL (Secure Sockets Layer) is a cryptographic protocol designed to provide secure, encrypted communication over a computer network, commonly used to protect data transmitted between clients and servers.
-
C.
PuTTY
PuTTY is a widely used free and open-source terminal emulator and network client for Windows and other platforms, supporting protocols like SSH, Telnet, and serial connections.
-
D.
Diffie–Hellman key exchange
Diffie–Hellman key exchange is a foundational cryptographic protocol that enables two parties to securely establish a shared secret over an insecure communication channel.
-
E.
TLS
TLS (Transport Layer Security) is a cryptographic protocol that secures data transmitted over networks by providing encryption, authentication, and integrity between communicating applications.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a25e2ddaa88190b08c40b5823f30a0 |
completed | Feb. 28, 2026, 3:17 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a39d078ad88190b4fce535c8ea9a80 |
completed | March 1, 2026, 1:57 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.