RFC 2045
E830593
RFC 2045 is an Internet standard that defines the format and encoding rules for MIME message bodies used in email and related Internet protocols.
All labels observed (4)
| Label | Occurrences |
|---|---|
| RFC 2045 canonical | 8 |
| MIME Part One | 1 |
| MIME message body format | 1 |
| Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T9931670 — 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 2045 Context triple: [MIME, standardizedIn, RFC 2045]
-
A.
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.
-
B.
RFC 1447
RFC 1447 is an early Internet standards document that specified mechanisms for managing SNMPv2 network management protocols before being superseded by later revisions.
-
C.
RFC 822
RFC 822 is an early Internet standard that defines the format of text-based email messages, including headers and addressing conventions.
-
D.
RFC 3821
RFC 3821 is an IETF standards document that specifies the Fibre Channel over TCP/IP (FCIP) protocol for transporting Fibre Channel frames over IP networks.
-
E.
RFC 3821
RFC 3821 is an Internet Engineering Task Force (IETF) standards document that specifies the Internet Fibre Channel Protocol (iFCP) for transporting Fibre Channel frames over 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 2045 Target entity description: RFC 2045 is an Internet standard that defines the format and encoding rules for MIME message bodies used in email and related Internet protocols.
-
A.
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.
-
B.
RFC 1447
RFC 1447 is an early Internet standards document that specified mechanisms for managing SNMPv2 network management protocols before being superseded by later revisions.
-
C.
RFC 822
RFC 822 is an early Internet standard that defines the format of text-based email messages, including headers and addressing conventions.
-
D.
RFC 3821
RFC 3821 is an IETF standards document that specifies the Fibre Channel over TCP/IP (FCIP) protocol for transporting Fibre Channel frames over IP networks.
-
E.
RFC 3821
RFC 3821 is an Internet Engineering Task Force (IETF) standards document that specifies the Internet Fibre Channel Protocol (iFCP) for transporting Fibre Channel frames over IP networks.
- F. None of above. chosen
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| appliesTo |
Internet email
ⓘ
SMTP message bodies ⓘ message bodies in Internet protocols ⓘ |
| area | Applications ⓘ |
| category | Standards Track ⓘ |
| defines |
Content-Transfer-Encoding header field
ⓘ
Content-Type header field ⓘ MIME content transfer encodings ⓘ MIME header fields ⓘ MIME message body format ⓘ
linked to:
RFC 2045
MIME versioning mechanism ⓘ canonical form of MIME entities ⓘ format of Internet message bodies ⓘ |
| definesHeaderField |
Content-Description
ⓘ
Content-ID ⓘ Content-Transfer-Encoding ⓘ
linked to:
Content-Transfer-Encoding header field
Content-Type ⓘ
linked to:
MIME
MIME-Version ⓘ
linked to:
MIME
|
| intendedFor |
email user agents
ⓘ
mail transfer agents ⓘ |
| MIMEPart | Part One ⓘ |
| obsoletedBy | RFC 5322 ⓘ |
| obsoletes |
RFC 1521
ⓘ
RFC 1522 ⓘ |
| partOf | MIME specification ⓘ |
| publicationMonth | November ⓘ |
| publicationYear | 1996 ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedTo |
RFC 2046
ⓘ
RFC 2047 ⓘ RFC 2048 ⓘ RFC 2049 ⓘ |
| RFCNumber | 2045 ⓘ |
| specifies |
7bit content transfer encoding
ⓘ
8bit content transfer encoding ⓘ Base64 content transfer encoding ⓘ Quoted-Printable content transfer encoding ⓘ binary content transfer encoding ⓘ |
| standardizes |
labeling of media types in Internet messages
ⓘ
representation of non-ASCII data in email ⓘ |
| status | Internet Standard ⓘ |
| STDNumber | STD 11 ⓘ |
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| title |
Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies
ⓘ
linked to:
RFC 2045
|
| updatesSpecificationOf | MIME ⓘ |
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 2045 Description of subject: RFC 2045 is an Internet standard that defines the format and encoding rules for MIME message bodies used in email and related Internet protocols.
Referenced by (11)
Full triples — surface form annotated when it differs from this entity's canonical label.