RFC 1022
E325857
RFC 1022 is an early Internet standards document that was later superseded by RFC 1122, which more comprehensively defines host requirements for Internet protocols.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 1022 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T3081733 — 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 1022 Context triple: [RFC 1122, obsoletes, RFC 1022]
-
A.
RFC 822
RFC 822 is an early Internet standard that defines the format of text-based email messages, including headers and addressing conventions.
-
B.
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.
-
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 883
RFC 883 was an early Internet standard that originally specified the Domain Name System (DNS) before being superseded by later DNS specifications.
-
E.
RFC 2821
RFC 2821 is an earlier Internet standard that defined the Simple Mail Transfer Protocol (SMTP) for email transmission before being superseded by RFC 5321.
- 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 1022 Target entity description: RFC 1022 is an early Internet standards document that was later superseded by RFC 1122, which more comprehensively defines host requirements for Internet protocols.
-
A.
RFC 822
RFC 822 is an early Internet standard that defines the format of text-based email messages, including headers and addressing conventions.
-
B.
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.
-
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 883
RFC 883 was an early Internet standard that originally specified the Domain Name System (DNS) before being superseded by later DNS specifications.
-
E.
RFC 2821
RFC 2821 is an earlier Internet standard that defined the Simple Mail Transfer Protocol (SMTP) for email transmission before being superseded by RFC 5321.
- F. None of above. chosen
Statements (25)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standards document
ⓘ
Request for Comments ⓘ |
| category | Standards Track ⓘ |
| defines | requirements for high-level protocols ⓘ |
| documentType | Technical specification ⓘ |
| hasRelation |
Host requirements for Internet protocols
ⓘ
TCP/IP ⓘ
surface form:
TCP/IP protocol suite
|
| hasRFCNumber | 1022 ⓘ |
| hasSuccessor | RFC 1122 ⓘ |
| hasTitle | The High-Level Protocol Standard ⓘ |
| isPartOf | Internet standards ⓘ |
| language | English ⓘ |
| medium | Electronic document ⓘ |
| obsoletedBy | RFC 1122 ⓘ |
| partOfSeries |
RFCs
ⓘ
surface form:
RFC series
|
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo |
Internet protocol standards
ⓘ
host requirements ⓘ |
| scope | Internet hosts ⓘ |
| seriesNumber | 1022 ⓘ |
| standardizes | aspects of Internet host behavior ⓘ |
| status | Obsoleted ⓘ |
| topic |
Internet architecture
ⓘ
protocol requirements ⓘ |
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 1022 Description of subject: RFC 1022 is an early Internet standards document that was later superseded by RFC 1122, which more comprehensively defines host requirements for Internet protocols.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.