RFC 883
E37188
RFC 883 was an early Internet standard that originally specified the Domain Name System (DNS) before being superseded by later DNS specifications.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 883 canonical | 5 |
How this entity was disambiguated
This entity first appeared as the object of triple T270988 — 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 883 Context triple: [RFC 1035, obsoletes, RFC 883]
-
A.
RFC 882
RFC 882 was an early Internet standard that originally specified the Domain Name System (DNS) protocol before being superseded by later RFCs such as RFC 1035.
-
B.
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.
-
C.
RFC 821
RFC 821 is the original Internet standard that formally defined the Simple Mail Transfer Protocol (SMTP) for electronic mail transmission.
-
D.
RFC 1939
RFC 1939 is the Internet standard document that specifies the Post Office Protocol version 3 (POP3) used for retrieving email from a mail server.
-
E.
RFC 792
RFC 792 is the Internet standard document that specifies the Internet Control Message Protocol (ICMP), which is used for network diagnostics and error reporting in 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 883 Target entity description: RFC 883 was an early Internet standard that originally specified the Domain Name System (DNS) before being superseded by later DNS specifications.
-
A.
RFC 882
RFC 882 was an early Internet standard that originally specified the Domain Name System (DNS) protocol before being superseded by later RFCs such as RFC 1035.
-
B.
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.
-
C.
RFC 821
RFC 821 is the original Internet standard that formally defined the Simple Mail Transfer Protocol (SMTP) for electronic mail transmission.
-
D.
RFC 1939
RFC 1939 is the Internet standard document that specifies the Post Office Protocol version 3 (POP3) used for retrieving email from a mail server.
-
E.
RFC 792
RFC 792 is the Internet standard document that specifies the Internet Control Message Protocol (ICMP), which is used for network diagnostics and error reporting in IP networks.
- F. None of above. chosen
Statements (38)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments document ⓘ |
| area |
the internet
ⓘ
surface form:
Internet
|
| author |
Paul Mockapetris
ⓘ
surface form:
Paul V. Mockapetris
|
| category | Standards Track ⓘ |
| context | transition from HOSTS.TXT to DNS ⓘ |
| defines |
guidelines for domain name resolvers
ⓘ
operational procedures for domain name servers ⓘ |
| hasNumber | 883 ⓘ |
| historicalRole | one of the first formal DNS specifications ⓘ |
| language | English ⓘ |
| networkScope |
ARPANET
ⓘ
early Internet ⓘ |
| obsoletedBy |
RFC 1034
ⓘ
RFC 1035 ⓘ |
| partOf | early DNS specifications ⓘ |
| predecessorOf |
RFC 1034
ⓘ
RFC 1035 ⓘ |
| protocolFamily | Domain Name System ⓘ |
| publicationDate | 1983-11 ⓘ |
| publicationYear | 1983 ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ Network Information Center ⓘ |
| replacedBy | modern DNS standards ⓘ |
| series |
RFCs
ⓘ
surface form:
RFC series
|
| specifies |
DNS implementation details
ⓘ
DNS message formats ⓘ DNS query and response behavior ⓘ DNS resource record handling ⓘ Domain Name System ⓘ |
| standardizes | use of domain names in the Internet ⓘ |
| status | Obsoleted ⓘ |
| title |
Domain Name System
ⓘ
surface form:
Domain Names - Implementation and Specification
|
| topic |
domain names
ⓘ
name servers ⓘ resolvers ⓘ |
| updates | early host name to address mapping mechanisms ⓘ |
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 883 Description of subject: RFC 883 was an early Internet standard that originally specified the Domain Name System (DNS) before being superseded by later DNS specifications.
Referenced by (5)
Full triples — surface form annotated when it differs from this entity's canonical label.
subject surface form:
Paul Mockapetris