RFC 1521
E807560
RFC 1521 is the foundational specification that defines the Multipurpose Internet Mail Extensions (MIME) standard for formatting and encoding multimedia email messages on the Internet.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 1521 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T9548199 — 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 1521 Context triple: [RFC 1652, relatedTo, RFC 1521]
-
A.
RFC 1541
RFC 1541 is an early Internet standards document that originally specified the Dynamic Host Configuration Protocol (DHCP) for automatic IP address assignment before being superseded by RFC 2131.
-
B.
RFC 1661
RFC 1661 is the original specification of the Point-to-Point Protocol (PPP), defining a standard method for transporting multi-protocol datagrams over point-to-point links.
-
C.
RFC 1652
RFC 1652 is an early Internet standards document that defines the 8BITMIME extension for SMTP, enabling the transfer of 8-bit character data in email.
-
D.
RFC 1591
RFC 1591 is an Internet standards document that defines the structure, administration, and delegation policies for top-level domains in the Domain Name System (DNS).
-
E.
RFC 1195
RFC 1195 is the IETF standard that extends the IS-IS routing protocol to support multiple network layer protocols, including IP.
- 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 1521 Target entity description: RFC 1521 is the foundational specification that defines the Multipurpose Internet Mail Extensions (MIME) standard for formatting and encoding multimedia email messages on the Internet.
-
A.
RFC 1541
RFC 1541 is an early Internet standards document that originally specified the Dynamic Host Configuration Protocol (DHCP) for automatic IP address assignment before being superseded by RFC 2131.
-
B.
RFC 1661
RFC 1661 is the original specification of the Point-to-Point Protocol (PPP), defining a standard method for transporting multi-protocol datagrams over point-to-point links.
-
C.
RFC 1652
RFC 1652 is an early Internet standards document that defines the 8BITMIME extension for SMTP, enabling the transfer of 8-bit character data in email.
-
D.
RFC 1591
RFC 1591 is an Internet standards document that defines the structure, administration, and delegation policies for top-level domains in the Domain Name System (DNS).
-
E.
RFC 1195
RFC 1195 is the IETF standard that extends the IS-IS routing protocol to support multiple network layer protocols, including IP.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard specification
ⓘ
Request for Comments ⓘ |
| abbreviation | MIME Part One NERFINISHED ⓘ |
| appliesTo |
Internet email
ⓘ
SMTP-based message transfer ⓘ |
| area | Applications ⓘ |
| category | Standards Track ⓘ |
| defines |
7bit content-transfer-encoding
ⓘ
8bit content-transfer-encoding ⓘ Content-Description header field ⓘ Content-ID header field ⓘ Content-Transfer-Encoding header field NERFINISHED ⓘ Content-Type header field ⓘ MIME boundary parameter ⓘ MIME entity ⓘ MIME-Version header field ⓘ Multipurpose Internet Mail Extensions NERFINISHED ⓘ application content type ⓘ audio content type ⓘ base64 content-transfer-encoding ⓘ binary content-transfer-encoding ⓘ body part ⓘ image content type ⓘ message content type ⓘ multipart content type ⓘ quoted-printable content-transfer-encoding ⓘ text content type ⓘ video content type ⓘ |
| isObsoletedBy |
RFC 2045
NERFINISHED
ⓘ
RFC 2046 NERFINISHED ⓘ |
| language | English ⓘ |
| obsoletes | RFC 1341 NERFINISHED ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| publishedInSeries | RFC series NERFINISHED ⓘ |
| relatedTo |
MIME
NERFINISHED
ⓘ
RFC 1522 ⓘ |
| specifies |
mechanisms for describing the format of Internet message bodies
ⓘ
mechanisms for encoding multimedia email messages ⓘ mechanisms for specifying the format of Internet message bodies ⓘ |
| standardizes |
MIME content types
NERFINISHED
ⓘ
MIME message headers ⓘ MIME transfer encodings ⓘ encoding of Internet message bodies ⓘ format of Internet message bodies ⓘ message body parts ⓘ multipart message structure ⓘ |
| status | Obsoleted ⓘ |
| title | MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies 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 1521 Description of subject: RFC 1521 is the foundational specification that defines the Multipurpose Internet Mail Extensions (MIME) standard for formatting and encoding multimedia email messages on the Internet.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.