RFC 1730
E282852
RFC 1730 is an early specification of the Internet Message Access Protocol (IMAP) that was later superseded by RFC 3501.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 1730 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T1881430 — 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 1730 Context triple: [RFC 3501, obsoletes, RFC 1730]
-
A.
RFC 1670
RFC 1670 is an early Internet standards document related to network protocols that was later superseded by RFC 1901.
-
B.
RFC 1350
RFC 1350 is the Internet standards document that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
-
C.
RFC 1660
RFC 1660 is an early Internet standards document that specified an initial version of the Simple Network Management Protocol (SNMP) over OSI transport services before being superseded by later RFCs.
-
D.
RFC 1657
RFC 1657 is an early Internet standards document that defined SNMPv2 Management Information Base (MIB) extensions for managing BGP-4 routing protocol implementations.
-
E.
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.
- 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 1730 Target entity description: RFC 1730 is an early specification of the Internet Message Access Protocol (IMAP) that was later superseded by RFC 3501.
-
A.
RFC 1670
RFC 1670 is an early Internet standards document related to network protocols that was later superseded by RFC 1901.
-
B.
RFC 1350
RFC 1350 is the Internet standards document that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
-
C.
RFC 1660
RFC 1660 is an early Internet standards document that specified an initial version of the Simple Network Management Protocol (SNMP) over OSI transport services before being superseded by later RFCs.
-
D.
RFC 1657
RFC 1657 is an early Internet standards document that defined SNMPv2 Management Information Base (MIB) extensions for managing BGP-4 routing protocol implementations.
-
E.
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.
- F. None of above. chosen
Statements (40)
| Predicate | Object |
|---|---|
| instanceOf |
Request for Comments
ⓘ
technical standard ⓘ |
| abbreviation |
IMAP4
ⓘ
linked to:
IMAP
|
| area | Applications ⓘ |
| category | Standards Track ⓘ |
| definesPortUsage | TCP port 143 by default for IMAP ⓘ |
| definesProtocolFor |
client access to email stored on a server
ⓘ
remote access to electronic mail ⓘ |
| documentSeries |
RFC series
ⓘ
linked to:
RFCs
|
| intendedAudience |
email client implementers
ⓘ
email server implementers ⓘ protocol designers ⓘ |
| intendedUse | Internet email ⓘ |
| language | English ⓘ |
| networkLayer | TCP/IP ⓘ |
| obsoletedBy | RFC 3501 ⓘ |
| protocolName |
IMAP4
ⓘ
linked to:
IMAP
|
| protocolSpecified |
Internet Message Access Protocol version 4
ⓘ
linked to:
IMAP
|
| protocolType | application-layer protocol ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedTo |
POP3
ⓘ
Post Office Protocol version 3 ⓘ
linked to:
POP3
SMTP ⓘ Simple Mail Transfer Protocol ⓘ
linked to:
SMTP
|
| scope | email message access and manipulation ⓘ |
| standardizes |
commands for managing message flags
ⓘ
commands for manipulating mailboxes ⓘ commands for retrieving email messages ⓘ commands for searching email messages ⓘ |
| status | Proposed Standard ⓘ |
| supportsFeature |
access to MIME-structured messages
ⓘ
message flags such as Seen and Answered ⓘ multiple mailboxes per user ⓘ online and offline message access ⓘ partial message fetch ⓘ server-side searching ⓘ |
| title |
IMAP4 Internet Message Access Protocol
ⓘ
linked to:
IMAP
|
| updates |
RFC 1064
ⓘ
RFC 1176 ⓘ |
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 1730 Description of subject: RFC 1730 is an early specification of the Internet Message Access Protocol (IMAP) that was later superseded by RFC 3501.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.