RFC 1443
E205080
RFC 1443 is an early Internet standards document that specified mechanisms for mapping between X.400 and RFC 822 email addressing and message formats.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 1443 canonical | 3 |
How this entity was disambiguated
This entity first appeared as the object of triple T1777466 — 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 1443 Context triple: [RFC 1901, obsoletes, RFC 1443]
-
A.
RFC 1441
RFC 1441 is an early standards-track document in the Simple Network Management Protocol (SNMP) framework that was later superseded by RFC 1901 as the protocol evolved.
-
B.
RFC 1813
RFC 1813 is the Internet Engineering Task Force (IETF) specification that defines version 3 of the Network File System (NFS) protocol.
-
C.
RFC 1094
RFC 1094 is the original specification document that standardizes the Network File System (NFS) protocol used for remote file access over a network.
-
D.
RFC 2449
RFC 2449 is an Internet standards document that extends the POP3 email protocol with additional capabilities and commands to improve flexibility and interoperability.
-
E.
RFC 1533
RFC 1533 is an early Internet standards document that originally specified DHCP and BOOTP vendor extensions and options before being superseded by later updates.
- 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 1443 Target entity description: RFC 1443 is an early Internet standards document that specified mechanisms for mapping between X.400 and RFC 822 email addressing and message formats.
-
A.
RFC 1441
RFC 1441 is an early standards-track document in the Simple Network Management Protocol (SNMP) framework that was later superseded by RFC 1901 as the protocol evolved.
-
B.
RFC 1813
RFC 1813 is the Internet Engineering Task Force (IETF) specification that defines version 3 of the Network File System (NFS) protocol.
-
C.
RFC 1094
RFC 1094 is the original specification document that standardizes the Network File System (NFS) protocol used for remote file access over a network.
-
D.
RFC 2449
RFC 2449 is an Internet standards document that extends the POP3 email protocol with additional capabilities and commands to improve flexibility and interoperability.
-
E.
RFC 1533
RFC 1533 is an early Internet standards document that originally specified DHCP and BOOTP vendor extensions and options before being superseded by later updates.
- F. None of above. chosen
Statements (34)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standards document
ⓘ
Request for Comments ⓘ technical specification ⓘ |
| area |
Internet mail
ⓘ
message handling systems ⓘ |
| category | Standards Track ⓘ |
| defines |
mapping of RFC 822 addresses to X.400(1988) / ISO 10021 addresses
ⓘ
mapping of RFC 822 message formats to X.400 message formats ⓘ mapping of X.400 message formats to RFC 822 message formats ⓘ mapping of X.400(1988) / ISO 10021 addresses to RFC 822 addresses ⓘ mechanisms for mapping between X.400 and RFC 822 ⓘ |
| focusesOn |
email interoperability
ⓘ
gatewaying between X.400 and RFC 822 ⓘ |
| intendedUse | implementation of X.400–RFC 822 gateways ⓘ |
| language | English ⓘ |
| obsoletedBy | RFC 2156 ⓘ |
| partOf | Internet Standards process ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| publishedInSeries |
Request for Comments
ⓘ
linked to:
RFCs
|
| relatedTo |
electronic mail
ⓘ
email address translation ⓘ email gateway design ⓘ message transfer systems ⓘ |
| relatesToProtocol |
RFC 822
ⓘ
X.400 ⓘ |
| relatesToStandard | ISO 10021 ⓘ |
| RFCNumber | 1443 ⓘ |
| standardizes |
address mapping rules
ⓘ
error handling for X.400 / RFC 822 gateways ⓘ message body and header mapping rules ⓘ |
| status | Proposed Standard ⓘ |
| title | Mapping between X.400(1988) / ISO 10021 and RFC 822 ⓘ |
| updates | RFC 1327 ⓘ |
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 1443 Description of subject: RFC 1443 is an early Internet standards document that specified mechanisms for mapping between X.400 and RFC 822 email addressing and message formats.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.