RFC 5322
E207723
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.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 5322 canonical | 3 |
How this entity was disambiguated
This entity first appeared as the object of triple T1866879 — 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 5322 Context triple: [RFC 5321, relatedTo, RFC 5322]
-
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 5321
RFC 5321 is the Internet standard that specifies the Simple Mail Transfer Protocol (SMTP) used for email transmission across 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 1123
RFC 1123 is an Internet standards document that refines and extends the requirements for host software, including DNS and related protocols, to ensure interoperability on the early Internet.
-
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 5322 Target entity description: 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.
-
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 5321
RFC 5321 is the Internet standard that specifies the Simple Mail Transfer Protocol (SMTP) used for email transmission across 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 1123
RFC 1123 is an Internet standards document that refines and extends the requirements for host software, including DNS and related protocols, to ensure interoperability on the early Internet.
-
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 (53)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments document ⓘ email message format specification ⓘ |
| area | Applications ⓘ |
| category | Standards Track ⓘ |
| defines |
ABNF grammar for email message format
ⓘ
RFC 822 ⓘ
surface form:
Internet message header fields
concept of origination date field ⓘ concept of resent messages ⓘ concept of trace information in email headers ⓘ format of Internet email message headers ⓘ syntax of text-based Internet email messages ⓘ |
| definesHeaderField |
Bcc
ⓘ
Cc ⓘ Comments ⓘ Date ⓘ From ⓘ In-Reply-To ⓘ Keywords ⓘ MIME ⓘ
surface form:
MIME-Version
Message-ID ⓘ Received ⓘ References ⓘ Reply-To ⓘ Resent-Date ⓘ Resent-From ⓘ Resent-Message-ID ⓘ Resent-To ⓘ Return-Path ⓘ Sender ⓘ Subject ⓘ To ⓘ |
| obsoletes | RFC 2822 ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo |
MIME
ⓘ
SMTP ⓘ SMTP ⓘ
surface form:
Simple Mail Transfer Protocol
|
| specifies |
rules for comments in header fields
ⓘ
rules for header field syntax ⓘ rules for line folding in headers ⓘ rules for whitespace in header fields ⓘ structure of email message headers and body ⓘ syntax for Resent- header fields ⓘ syntax for dates and times in email headers ⓘ syntax for display names in email addresses ⓘ syntax for email addresses ⓘ syntax for message identifiers ⓘ syntax for optional header fields ⓘ syntax for trace fields such as Received ⓘ |
| status | Internet Standard ⓘ |
| title |
RFC 2822
ⓘ
surface form:
Internet Message Format
|
| updates | RFC 822 ⓘ |
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 5322 Description of subject: 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.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.