RFC 877
E207057
RFC 877 is an early Internet standards document that specifies the standard for Internet Control Message Protocol (ICMP) echo messages used for network diagnostics such as the "ping" utility.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 877 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1631619 — 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 877 Context triple: [RFC 854, relatedRFC, RFC 877]
-
A.
RFC 870
RFC 870 is an early Internet standards document that refines and extends the Telnet protocol specifications originally defined in RFC 854.
-
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 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 875
RFC 875 is an early Internet standard document that refines and extends the Telnet protocol specifications to improve interoperability and functionality in remote terminal connections.
-
E.
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.
- 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 877 Target entity description: RFC 877 is an early Internet standards document that specifies the standard for Internet Control Message Protocol (ICMP) echo messages used for network diagnostics such as the "ping" utility.
-
A.
RFC 870
RFC 870 is an early Internet standards document that refines and extends the Telnet protocol specifications originally defined in RFC 854.
-
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 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 875
RFC 875 is an early Internet standard document that refines and extends the Telnet protocol specifications to improve interoperability and functionality in remote terminal connections.
-
E.
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.
- F. None of above. chosen
Statements (26)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard document
ⓘ
Request for Comments ⓘ |
| appliesTo |
Ethernet LANs
ⓘ
local area networks ⓘ |
| area |
the internet
ⓘ
surface form:
Internet
|
| category | Internet protocol standard ⓘ |
| defines |
maximum transmission unit for IP over Ethernet
ⓘ
standard for transmission of IP datagrams over Ethernet ⓘ use of Ethernet type field for IP datagrams ⓘ |
| documentType | Standards Track RFC ⓘ |
| hasNumber | 877 ⓘ |
| language | English ⓘ |
| obsoletedBy |
RFC 1042
ⓘ
RFC 894 ⓘ |
| partOfSeries | RFC series ⓘ |
| publishedBy |
Internet Activities Board
ⓘ
Internet Engineering Task Force ⓘ |
| relatedToProtocol | Internet Protocol ⓘ |
| relatedToTechnology | Ethernet ⓘ |
| series | STD 37 ⓘ |
| specifies | encapsulation of IP datagrams on Ethernet networks ⓘ |
| standardizes | format for IP over Ethernet frames ⓘ |
| status | Historic ⓘ |
| title | A Standard for the Transmission of IP Datagrams on Ethernet Networks ⓘ |
| topic |
IP over Ethernet
ⓘ
network layer encapsulation ⓘ |
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 877 Description of subject: RFC 877 is an early Internet standards document that specifies the standard for Internet Control Message Protocol (ICMP) echo messages used for network diagnostics such as the "ping" utility.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.