RFC 2822
E708917
RFC 2822 is an Internet standard that defines the format for text-based email messages, updating and replacing the earlier RFC 822 specification.
All labels observed (2)
| Label | Occurrences |
|---|---|
| RFC 2822 canonical | 4 |
| Internet Message Format | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T8035942 — 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 2822 Context triple: [RFC 822, obsoletedBy, RFC 2822]
-
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 5322
RFC 5322 is the Internet standard that defines the syntax and format of text-based email messages, including headers such as From, To, Subject, and Date.
-
C.
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.
-
D.
RFC 1022
RFC 1022 is an early Internet standards document that was later superseded by RFC 1122, which more comprehensively defines host requirements for Internet protocols.
-
E.
RFC 5321
RFC 5321 is the Internet standard that specifies the Simple Mail Transfer Protocol (SMTP) used for email transmission across 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 2822 Target entity description: RFC 2822 is an Internet standard that defines the format for text-based email messages, updating and replacing the earlier RFC 822 specification.
-
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 5322
RFC 5322 is the Internet standard that defines the syntax and format of text-based email messages, including headers such as From, To, Subject, and Date.
-
C.
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.
-
D.
RFC 1022
RFC 1022 is an early Internet standards document that was later superseded by RFC 1122, which more comprehensively defines host requirements for Internet protocols.
-
E.
RFC 5321
RFC 5321 is the Internet standard that specifies the Simple Mail Transfer Protocol (SMTP) used for email transmission across IP networks.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments document ⓘ |
| appliesTo |
Internet email
ⓘ
SMTP-transmitted messages ⓘ |
| area | Applications ⓘ |
| category | Standards Track ⓘ |
| defines |
addressing syntax for email messages
ⓘ
comments in header fields ⓘ date and time specification for email messages ⓘ folding of long header fields ⓘ format for text-based email messages ⓘ line length limits for email headers ⓘ message body structure for Internet email ⓘ semantics for Internet email headers ⓘ syntax for Internet email headers ⓘ white space handling in header fields ⓘ |
| definesField |
Bcc header field
ⓘ
Cc header field ⓘ Date header field ⓘ From header field ⓘ In-Reply-To header field ⓘ Message-ID header field ⓘ Received header field ⓘ References header field ⓘ Reply-To header field NERFINISHED ⓘ Resent-* header fields ⓘ Sender header field ⓘ Subject header field ⓘ To header field ⓘ |
| doesNotDefine |
MIME content types
ⓘ
message transport ⓘ |
| language | English ⓘ |
| obsoletedBy | RFC 5322 NERFINISHED ⓘ |
| obsoletes | RFC 822 NERFINISHED ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo |
RFC 5321
NERFINISHED
ⓘ
SMTP NERFINISHED ⓘ |
| replaces | RFC 822 NERFINISHED ⓘ |
| RFCNumber | 2822 ⓘ |
| scope | syntax and semantics of Internet message headers ⓘ |
| specifies | ABNF grammar for email message format ⓘ |
| standardizes | Internet message format NERFINISHED ⓘ |
| status | Obsoleted ⓘ |
| title | Internet Message Format NERFINISHED ⓘ |
| updates | RFC 822 NERFINISHED ⓘ |
| updatesProtocol | Internet Message Format NERFINISHED ⓘ |
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 2822 Description of subject: RFC 2822 is an Internet standard that defines the format for text-based email messages, updating and replacing the earlier RFC 822 specification.
Referenced by (5)
Full triples — surface form annotated when it differs from this entity's canonical label.