RFC 858
E187108
RFC 858 is an early Internet standard that defines the Telnet protocol’s status option, specifying how a Telnet client and server can exchange information about their current status.
All labels observed (2)
How this entity was disambiguated
This entity first appeared as the object of triple T1631600 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 858 Context triple: [RFC 854, relatedRFC, RFC 858]
-
A.
RFC 855
RFC 855 is an Internet standards document that specifies the Telnet protocol’s options and mechanisms for remote terminal communication over TCP/IP networks.
-
B.
RFC 857
RFC 857 is an Internet standard that defines the Telnet protocol option for echoing characters, specifying how user input is echoed back in Telnet sessions.
-
C.
RFC 783
RFC 783 is the original specification that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
-
D.
RFC 5308
RFC 5308 is the Internet Engineering Task Force (IETF) specification that extends the IS-IS routing protocol to support IPv6 addressing and routing.
-
E.
RFC 883
RFC 883 was an early Internet standard that originally specified the Domain Name System (DNS) before being superseded by later DNS specifications.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 858 Target entity description: RFC 858 is an early Internet standard that defines the Telnet protocol’s status option, specifying how a Telnet client and server can exchange information about their current status.
-
A.
RFC 855
RFC 855 is an Internet standards document that specifies the Telnet protocol’s options and mechanisms for remote terminal communication over TCP/IP networks.
-
B.
RFC 857
RFC 857 is an Internet standard that defines the Telnet protocol option for echoing characters, specifying how user input is echoed back in Telnet sessions.
-
C.
RFC 783
RFC 783 is the original specification that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
-
D.
RFC 5308
RFC 5308 is the Internet Engineering Task Force (IETF) specification that extends the IS-IS routing protocol to support IPv6 addressing and routing.
-
E.
RFC 883
RFC 883 was an early Internet standard that originally specified the Domain Name System (DNS) before being superseded by later DNS specifications.
- F. None of above. chosen
Statements (32)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ Telnet protocol specification ⓘ |
| appliesTo |
Telnet clients
ⓘ
Telnet servers ⓘ |
| area | Application layer ⓘ |
| category | Standards Track ⓘ |
| defines | Telnet status option ⓘ |
| definesConcept |
requesting status of Telnet options
ⓘ
sending current status of Telnet options ⓘ |
| definesDirection |
client-to-server status reporting
ⓘ
server-to-client status reporting ⓘ |
| definesOption | STATUS ⓘ |
| documentType | technical specification ⓘ |
| focusesOn | control information exchange rather than user data ⓘ |
| intendedAudience |
Telnet client developers
ⓘ
Telnet server developers ⓘ network protocol implementers ⓘ |
| language | English ⓘ |
| layer | application layer of the Internet protocol suite ⓘ |
| protocol | Telnet ⓘ |
| publishedBy |
Internet Activities Board
ⓘ
Internet Engineering Task Force ⓘ |
| relatedTo |
RFC 854
ⓘ
Telnet ⓘ
surface form:
Telnet protocol
|
| series | RFC ⓘ |
| specifies | mechanism for exchanging status information between Telnet client and server ⓘ |
| standardizes |
format of Telnet STATUS messages
ⓘ
semantics of Telnet STATUS option ⓘ |
| status | Internet Standard ⓘ |
| title | Telnet Status Option ⓘ |
| updates | Telnet protocol options ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: RFC 858 Description of subject: RFC 858 is an early Internet standard that defines the Telnet protocol’s status option, specifying how a Telnet client and server can exchange information about their current status.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.
this entity surface form:
RFC 859