RFC 870
E201928
RFC 870 is an early Internet standards document that refines and extends the Telnet protocol specifications originally defined in RFC 854.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 870 canonical | 6 |
How this entity was disambiguated
This entity first appeared as the object of triple T1631612 — 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 870 Context triple: [RFC 854, relatedRFC, RFC 870]
-
A.
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.
-
B.
RFC 860
RFC 860 is an Internet standard that defines the Telnet Timing Mark option, used to synchronize and manage timing in Telnet connections.
-
C.
RFC 867
RFC 867 is an early Internet standard that defines the "Daytime Protocol," a simple service for returning the current date and time over a network connection.
-
D.
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.
-
E.
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.
- 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 870 Target entity description: RFC 870 is an early Internet standards document that refines and extends the Telnet protocol specifications originally defined in RFC 854.
-
A.
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.
-
B.
RFC 860
RFC 860 is an Internet standard that defines the Telnet Timing Mark option, used to synchronize and manage timing in Telnet connections.
-
C.
RFC 867
RFC 867 is an early Internet standard that defines the "Daytime Protocol," a simple service for returning the current date and time over a network connection.
-
D.
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.
-
E.
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.
- F. None of above. chosen
Statements (34)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ technical specification ⓘ |
| area |
Internet protocol architecture
ⓘ
linked to:
Internet architecture
|
| category | Internet protocol parameters ⓘ |
| defines |
assigned link numbers
ⓘ
assigned numbers for Internet protocols ⓘ assigned port numbers ⓘ assigned protocol numbers ⓘ assigned socket numbers ⓘ |
| documentSeries |
RFC
ⓘ
linked to:
RFCs
|
| hasRFCNumber | 870 ⓘ |
| intendedAudience |
network implementers
ⓘ
protocol designers ⓘ system administrators ⓘ |
| language | English ⓘ |
| obsoletedBy |
RFC 1010
ⓘ
RFC 1060 ⓘ RFC 1340 ⓘ RFC 1700 ⓘ RFC 3232 ⓘ RFC 923 ⓘ RFC 943 ⓘ RFC 960 ⓘ RFC 990 ⓘ |
| partOf |
Assigned Numbers series
ⓘ
linked to:
Internet Assigned Numbers Authority
|
| publicationYear | 1983 ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ Network Working Group ⓘ |
| standardizes | Internet protocol parameter assignments ⓘ |
| status | Historic ⓘ |
| title |
Assigned Numbers
ⓘ
linked to:
Internet Assigned Numbers Authority
|
| updates | RFC 790 ⓘ |
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 870 Description of subject: RFC 870 is an early Internet standards document that refines and extends the Telnet protocol specifications originally defined in RFC 854.
Referenced by (6)
Full triples — surface form annotated when it differs from this entity's canonical label.