RFC 1651
E227543
RFC 1651 is an early Internet standards document that defined extensions to the Simple Mail Transfer Protocol (SMTP) to support enhanced email functionality.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 1651 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T1777481 — 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 1651 Context triple: [RFC 1901, obsoletes, RFC 1651]
-
A.
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).
-
B.
RFC 1906
RFC 1906 is an Internet standard that specifies the transport mappings for SNMPv2, detailing how SNMP messages are carried over various network protocols.
-
C.
RFC 1195
RFC 1195 is the IETF standard that extends the IS-IS routing protocol to support multiple network layer protocols, including IP.
-
D.
RFC 1813
RFC 1813 is the Internet Engineering Task Force (IETF) specification that defines version 3 of the Network File System (NFS) protocol.
-
E.
RFC 2571
RFC 2571 was an earlier specification in the Simple Network Management Protocol (SNMP) framework that was later superseded and updated by RFC 3411.
- 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 1651 Target entity description: RFC 1651 is an early Internet standards document that defined extensions to the Simple Mail Transfer Protocol (SMTP) to support enhanced email functionality.
-
A.
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).
-
B.
RFC 1906
RFC 1906 is an Internet standard that specifies the transport mappings for SNMPv2, detailing how SNMP messages are carried over various network protocols.
-
C.
RFC 1195
RFC 1195 is the IETF standard that extends the IS-IS routing protocol to support multiple network layer protocols, including IP.
-
D.
RFC 1813
RFC 1813 is the Internet Engineering Task Force (IETF) specification that defines version 3 of the Network File System (NFS) protocol.
-
E.
RFC 2571
RFC 2571 was an earlier specification in the Simple Network Management Protocol (SNMP) framework that was later superseded and updated by RFC 3411.
- F. None of above. chosen
Statements (31)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standards document
ⓘ
Request for Comments ⓘ |
| abbreviation | RFC 1651 ⓘ |
| area | Applications ⓘ |
| category | Standards Track RFC ⓘ |
| defines | SMTP service extensions ⓘ |
| definesConcept |
ESMTP
ⓘ
linked to:
IETF ESMTP Working Group
Extended SMTP ⓘ
linked to:
SMTP
|
| definesField |
ESMTP keyword advertisement
ⓘ
SMTP extension parameters ⓘ |
| definesMechanism |
SMTP EHLO command
ⓘ
SMTP extension advertisement ⓘ negotiation of SMTP service extensions ⓘ |
| definesRequirementLevel |
mandatory-to-implement base SMTP
ⓘ
optional SMTP extensions ⓘ |
| documentType | Standards specification ⓘ |
| extends |
Simple Mail Transfer Protocol
ⓘ
linked to:
SMTP
|
| language | English ⓘ |
| networkLayer | Application layer of the Internet protocol suite ⓘ |
| obsoletedBy | RFC 1869 ⓘ |
| protocolFamily |
Application layer
ⓘ
Email ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| purpose | to support enhanced email functionality ⓘ |
| relatedTo |
RFC 1869
ⓘ
RFC 821 ⓘ |
| standardizes | framework for SMTP extensions ⓘ |
| status | Obsoleted ⓘ |
| title |
SMTP Service Extensions
ⓘ
linked to:
SMTP AUTH
|
| updatesProtocol | SMTP ⓘ |
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 1651 Description of subject: RFC 1651 is an early Internet standards document that defined extensions to the Simple Mail Transfer Protocol (SMTP) to support enhanced email functionality.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.