Triple
T63788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SSH |
E1267
|
entity |
| Predicate | definedIn |
P775
|
FINISHED |
| Object |
RFC 4253
RFC 4253 is the Internet standard that specifies the Secure Shell (SSH) transport layer protocol, including encryption, key exchange, and server authentication mechanisms.
|
E7607
|
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: RFC 4253 | Statement: [SSH, definedIn, RFC 4253]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 4253 Context triple: [SSH, definedIn, RFC 4253]
-
A.
RFC 4251
RFC 4251 is the core specification that defines the architecture and protocol framework of the Secure Shell (SSH) protocol used for secure remote communication.
-
B.
RFC 4252
RFC 4252 is an Internet standard that specifies the authentication protocol used by Secure Shell (SSH) for secure remote login and other network services.
-
C.
RFC 5246
RFC 5246 is the Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) version 1.2, a widely used protocol for securing communications over computer networks.
-
D.
RFC 8446
RFC 8446 is the Internet standard that specifies TLS 1.3, a major revision of the Transport Layer Security protocol focused on improved security and performance for encrypted communications.
-
E.
RFC 9112
RFC 9112 is the IETF specification that standardizes the semantics and behavior of HTTP/1.1.
- 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: RFC 4253 Triple: [SSH, definedIn, RFC 4253]
Generated description
RFC 4253 is the Internet standard that specifies the Secure Shell (SSH) transport layer protocol, including encryption, key exchange, and server authentication mechanisms.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 4253 Target entity description: RFC 4253 is the Internet standard that specifies the Secure Shell (SSH) transport layer protocol, including encryption, key exchange, and server authentication mechanisms.
-
A.
RFC 4251
RFC 4251 is the core specification that defines the architecture and protocol framework of the Secure Shell (SSH) protocol used for secure remote communication.
-
B.
RFC 4252
RFC 4252 is an Internet standard that specifies the authentication protocol used by Secure Shell (SSH) for secure remote login and other network services.
-
C.
RFC 5246
RFC 5246 is the Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) version 1.2, a widely used protocol for securing communications over computer networks.
-
D.
RFC 8446
RFC 8446 is the Internet standard that specifies TLS 1.3, a major revision of the Transport Layer Security protocol focused on improved security and performance for encrypted communications.
-
E.
RFC 9112
RFC 9112 is the IETF specification that standardizes the semantics and behavior of HTTP/1.1.
- 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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
| NER | Named-entity recognition | batch_69a24ee576fc8190b42e5d50767beefb |
completed | Feb. 28, 2026, 2:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a262406a6c81909be211fb2418ccbb |
completed | Feb. 28, 2026, 3:34 a.m. |
| NEDg | Description generation | batch_69a262d263508190a5924595c1a7ad28 |
completed | Feb. 28, 2026, 3:36 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69a2633ee14c8190bfc1a09ebf9e4efc |
completed | Feb. 28, 2026, 3:38 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.