RFC 1642
E453729
RFC 1642 is an Internet standards document that defines the UTF-7 encoding for representing Unicode characters in environments restricted to 7-bit data.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 1642 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T4575430 — 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 1642 Context triple: [UTF-7, introducedInStandard, RFC 1642]
-
A.
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.
-
B.
RFC 1664
RFC 1664 is an early Internet standards document that defined a now-obsolete mechanism related to email or messaging services, later superseded by RFC 1901.
-
C.
RFC 1670
RFC 1670 is an early Internet standards document related to network protocols that was later superseded by RFC 1901.
-
D.
RFC 1659
RFC 1659 is an early Internet standards document that specified the Simple Network Management Protocol (SNMP) version 2 over OSI transport mappings before being superseded by later revisions.
-
E.
RFC 1663
RFC 1663 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for serial line communication.
- 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 1642 Target entity description: RFC 1642 is an Internet standards document that defines the UTF-7 encoding for representing Unicode characters in environments restricted to 7-bit data.
-
A.
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.
-
B.
RFC 1664
RFC 1664 is an early Internet standards document that defined a now-obsolete mechanism related to email or messaging services, later superseded by RFC 1901.
-
C.
RFC 1670
RFC 1670 is an early Internet standards document related to network protocols that was later superseded by RFC 1901.
-
D.
RFC 1659
RFC 1659 is an early Internet standards document that specified the Simple Network Management Protocol (SNMP) version 2 over OSI transport mappings before being superseded by later revisions.
-
E.
RFC 1663
RFC 1663 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for serial line communication.
- F. None of above. chosen
Statements (30)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standards document
ⓘ
Request for Comments ⓘ |
| applicableTo | 7-bit data environments ⓘ |
| area | Applications ⓘ |
| category | Informational ⓘ |
| constraint | designed for 7-bit transport channels ⓘ |
| defines | UTF-7 ⓘ |
| definesEncodingFor | Unicode ⓘ |
| definesPropertyOfUTF-7 |
ASCII text remains readable
ⓘ
non-ASCII characters encoded using shift sequences ⓘ |
| encodingType | 7-bit safe encoding ⓘ |
| hasNumber | 1642 ⓘ |
| language | English ⓘ |
| motivatedBy | limitations of 7-bit email transport ⓘ |
| obsoletedBy | RFC 2152 ⓘ |
| primaryUseCase | encoding Unicode text in email ⓘ |
| proposes | UTF-7 as an encoding for Unicode over SMTP ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedTo |
Internet mail
ⓘ
MIME ⓘ SMTP ⓘ Unicode ⓘ character encoding ⓘ email systems ⓘ |
| series | RFC series ⓘ |
| standardizes | mail-safe transformation format for Unicode ⓘ |
| status | Historic ⓘ |
| title |
UTF-7: A Mail-Safe Transformation Format of Unicode
ⓘ
linked to:
UTF-7
|
| usesAlphabet | modified Base64 ⓘ |
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 1642 Description of subject: RFC 1642 is an Internet standards document that defines the UTF-7 encoding for representing Unicode characters in environments restricted to 7-bit data.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.