RFC 822
E187107
RFC 822 is an early Internet standard that defines the format of text-based email messages, including headers and addressing conventions.
All labels observed (2)
| Label | Occurrences |
|---|---|
| RFC 822 canonical | 21 |
| Internet message header fields | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1631437 — 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 822 Context triple: [RFC 821, messageFormatSpecifiedBy, RFC 822]
-
A.
RFC 821
RFC 821 is the original Internet standard that formally defined the Simple Mail Transfer Protocol (SMTP) for electronic mail transmission.
-
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 5321
RFC 5321 is the Internet standard that specifies the Simple Mail Transfer Protocol (SMTP) used for email transmission across IP networks.
-
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 3501
RFC 3501 is the Internet standard specification that defines version 4rev1 of the Internet Message Access Protocol (IMAP) used for accessing and managing email on 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 822 Target entity description: RFC 822 is an early Internet standard that defines the format of text-based email messages, including headers and addressing conventions.
-
A.
RFC 821
RFC 821 is the original Internet standard that formally defined the Simple Mail Transfer Protocol (SMTP) for electronic mail transmission.
-
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 5321
RFC 5321 is the Internet standard that specifies the Simple Mail Transfer Protocol (SMTP) used for email transmission across IP networks.
-
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 3501
RFC 3501 is the Internet standard specification that defines version 4rev1 of the Internet Message Access Protocol (IMAP) used for accessing and managing email on a mail server.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments document ⓘ email message format specification ⓘ |
| appliesTo | text-based email messages ⓘ |
| area | Applications ⓘ |
| author | David H. Crocker ⓘ |
| basedOn | RFC 733 ⓘ |
| category | Standards Track ⓘ |
| context |
ARPA Internet
ⓘ
linked to:
ARPANET
|
| defines |
addressing conventions for email
ⓘ
format of ARPA Internet text messages ⓘ rules for message bodies as text ⓘ syntax of email message headers ⓘ |
| documentNumber | 822 ⓘ |
| hasSection |
Address Specification
ⓘ
Message Header Fields ⓘ Semantics ⓘ Syntax ⓘ |
| historicStatus | Historic ⓘ |
| influenced |
RFC 2822
ⓘ
RFC 5322 ⓘ |
| intendedAudience |
Internet protocol designers
ⓘ
email system implementers ⓘ |
| language | English ⓘ |
| obsoletedBy |
RFC 2822
ⓘ
RFC 5322 ⓘ |
| protocolFamily | Internet mail ⓘ |
| publicationDate | 1982-08 ⓘ |
| publishedBy |
Internet Activities Board
ⓘ
Internet Engineering Task Force ⓘ |
| publisher | RFC Editor ⓘ |
| relatedTo |
SMTP
ⓘ
Simple Mail Transfer Protocol ⓘ
linked to:
SMTP
|
| replaces | RFC 733 ⓘ |
| scope | message format, not transport ⓘ |
| series |
Request for Comments
ⓘ
linked to:
RFCs
|
| specifies |
address specification syntax
ⓘ
date and time format in email headers ⓘ header field structure ⓘ message identification fields ⓘ optional informational header fields ⓘ trace fields such as Received ⓘ |
| standardizes | ARPA Internet text message format ⓘ |
| status | Obsoleted ⓘ |
| title | Standard for the Format of ARPA Internet Text Messages ⓘ |
| updates | RFC 733 ⓘ |
| usesCharacterSet | US-ASCII ⓘ |
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 822 Description of subject: RFC 822 is an early Internet standard that defines the format of text-based email messages, including headers and addressing conventions.
Referenced by (22)
Full triples — surface form annotated when it differs from this entity's canonical label.