RFC 2046
E832817
RFC 2046 is an Internet standard that defines the structure and types of media content used in the Multipurpose Internet Mail Extensions (MIME) framework.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 2046 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T9931671 — 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 2046 Context triple: [MIME, standardizedIn, RFC 2046]
-
A.
RFC 2045
RFC 2045 is an Internet standard that defines the format and encoding rules for MIME message bodies used in email and related Internet protocols.
-
B.
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.
-
C.
MIME
MIME (Multipurpose Internet Mail Extensions) is an internet standard that extends the format of email to support text in character sets beyond ASCII, as well as attachments like images, audio, video, and application files.
-
D.
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.
-
E.
RFC 2048
RFC 2048 is an Internet standards document that defines the registration procedures and guidelines for MIME media types and related parameters.
- 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 2046 Target entity description: RFC 2046 is an Internet standard that defines the structure and types of media content used in the Multipurpose Internet Mail Extensions (MIME) framework.
-
A.
RFC 2045
RFC 2045 is an Internet standard that defines the format and encoding rules for MIME message bodies used in email and related Internet protocols.
-
B.
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.
-
C.
MIME
MIME (Multipurpose Internet Mail Extensions) is an internet standard that extends the format of email to support text in character sets beyond ASCII, as well as attachments like images, audio, video, and application files.
-
D.
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.
-
E.
RFC 2048
RFC 2048 is an Internet standards document that defines the registration procedures and guidelines for MIME media types and related parameters.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| appliesTo |
MIME framework
ⓘ
email message bodies ⓘ |
| area | Internet mail ⓘ |
| category | Standards Track ⓘ |
| defines |
MIME media types
ⓘ
default media type text/plain ⓘ message/rfc822 media type ⓘ rules for registering new MIME media types ⓘ structure of media content for MIME ⓘ top-level MIME media type registry ⓘ |
| definesTopLevelType |
application
ⓘ
audio ⓘ image ⓘ message ⓘ multipart ⓘ text ⓘ video ⓘ |
| language | English ⓘ |
| obsoletes | RFC 1521 NERFINISHED ⓘ |
| partOfSeries | MIME specification NERFINISHED ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo |
RFC 2045
NERFINISHED
ⓘ
RFC 2047 NERFINISHED ⓘ RFC 822 NERFINISHED ⓘ |
| RFCNumber | 2046 ⓘ |
| specifies |
default values for MIME parameters
ⓘ
handling of unknown MIME subtypes ⓘ semantics of multipart/alternative ⓘ semantics of multipart/digest ⓘ semantics of multipart/mixed ⓘ semantics of multipart/parallel ⓘ semantics of multipart/related ⓘ syntax for MIME media type names ⓘ use of Content-Transfer-Encoding with media types ⓘ use of Content-Type header field ⓘ use of boundary parameter in multipart types ⓘ use of character sets in text media types ⓘ |
| standardizes | media content types for Internet mail ⓘ |
| status | Internet Standard ⓘ |
| title | Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types NERFINISHED ⓘ |
| updates | RFC 1521 NERFINISHED ⓘ |
| usedIn |
HTTP content-type handling
ⓘ
email clients ⓘ web servers ⓘ |
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 2046 Description of subject: RFC 2046 is an Internet standard that defines the structure and types of media content used in the Multipurpose Internet Mail Extensions (MIME) framework.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.