RFC 973
E192641
RFC 973 is an early Internet standards document that refines and extends the domain name system concepts introduced in RFC 882.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 973 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1695862 — 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 973 Context triple: [RFC 882, relatedTo, RFC 973]
-
A.
RFC 950
RFC 950 is an Internet standard that defines the procedures and format for subnetting IP networks, extending the original IPv4 addressing scheme.
-
B.
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.
-
C.
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.
-
D.
RFC 1195
RFC 1195 is the IETF standard that extends the IS-IS routing protocol to support multiple network layer protocols, including IP.
-
E.
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.
- 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 973 Target entity description: RFC 973 is an early Internet standards document that refines and extends the domain name system concepts introduced in RFC 882.
-
A.
RFC 950
RFC 950 is an Internet standard that defines the procedures and format for subnetting IP networks, extending the original IPv4 addressing scheme.
-
B.
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.
-
C.
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.
-
D.
RFC 1195
RFC 1195 is the IETF standard that extends the IS-IS routing protocol to support multiple network layer protocols, including IP.
-
E.
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.
- F. None of above. chosen
Statements (45)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard document
ⓘ
Request for Comments ⓘ technical specification ⓘ |
| author |
J. K. Reynolds
ⓘ
Jonathan B. Postel ⓘ
surface form:
J. Postel
|
| category | Domain Name System ⓘ |
| clarifies |
interactions between DNS components
ⓘ
operational aspects of DNS ⓘ |
| contributesTo | evolution of the Domain Name System ⓘ |
| discusses |
DNS implementation issues
ⓘ
DNS operational experience ⓘ DNS protocol clarifications ⓘ |
| documentType | standards-track document (at time of publication) ⓘ |
| extendsConceptsFrom | RFC 882 ⓘ |
| focusesOn |
domain system changes
ⓘ
domain system observations ⓘ |
| format | text ⓘ |
| hasPageFormat | ASCII ⓘ |
| hasRFCNumber | 973 ⓘ |
| hasURL | https://www.rfc-editor.org/rfc/rfc973 ⓘ |
| intendedAudience |
network implementers
ⓘ
protocol designers ⓘ system administrators ⓘ |
| isObsoletedBy | later DNS RFCs ⓘ |
| language | English ⓘ |
| mentions |
name servers
ⓘ
resource records ⓘ zones ⓘ |
| networkContext |
ARPANET
ⓘ
early Internet ⓘ |
| partOf | early DNS specification set ⓘ |
| publicationMonth | January ⓘ |
| publicationYear | 1986 ⓘ |
| publishedBy | RFC Editor ⓘ |
| publisher | Internet Engineering Task Force ⓘ |
| refinesConceptsFrom | RFC 882 ⓘ |
| relatedTo | Domain Name System ⓘ |
| series |
RFCs
ⓘ
surface form:
Request for Comments
|
| standardizes | aspects of the early Domain Name System ⓘ |
| status | Historic ⓘ |
| subjectArea |
Internet protocols
ⓘ
naming and addressing ⓘ |
| title |
Domain Name System root zone
ⓘ
surface form:
Domain System Changes and Observations
|
| updates |
RFC 882
ⓘ
RFC 883 ⓘ |
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 973 Description of subject: RFC 973 is an early Internet standards document that refines and extends the domain name system concepts introduced in RFC 882.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.