RFC 733
E708918
RFC 733 is an early Internet standard that defined the format for ARPA network text messages, serving as a foundational specification for modern email message structure.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 733 canonical | 3 |
How this entity was disambiguated
This entity first appeared as the object of triple T8035944 — 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 733 Context triple: [RFC 822, updates, RFC 733]
-
A.
RFC 973
RFC 973 is an early Internet standards document that refines and extends the domain name system concepts introduced in RFC 882.
-
B.
RFC 783
RFC 783 is the original specification that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
-
C.
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.
-
D.
RFC 1730
RFC 1730 is an early specification of the Internet Message Access Protocol (IMAP) that was later superseded by RFC 3501.
-
E.
RFC 1072
RFC 1072 is an early TCP/IP standards document that introduced experimental TCP extensions for high-performance and long-delay networks.
- 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 733 Target entity description: RFC 733 is an early Internet standard that defined the format for ARPA network text messages, serving as a foundational specification for modern email message structure.
-
A.
RFC 973
RFC 973 is an early Internet standards document that refines and extends the domain name system concepts introduced in RFC 882.
-
B.
RFC 783
RFC 783 is the original specification that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
-
C.
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.
-
D.
RFC 1730
RFC 1730 is an early specification of the Internet Message Access Protocol (IMAP) that was later superseded by RFC 3501.
-
E.
RFC 1072
RFC 1072 is an early TCP/IP standards document that introduced experimental TCP extensions for high-performance and long-delay networks.
- F. None of above. chosen
Statements (36)
| Predicate | Object |
|---|---|
| instanceOf |
Request for Comments document
ⓘ
email message format specification ⓘ |
| appliesTo |
store-and-forward messaging systems
ⓘ
text-based electronic mail ⓘ |
| area |
Internet
ⓘ
linked to:
the internet
|
| audience |
ARPANET researchers
ⓘ
email system implementers ⓘ network protocol designers ⓘ |
| category |
email
ⓘ
message format ⓘ |
| defines |
format of ARPA network text messages
ⓘ
structure of Internet email messages ⓘ syntax for email message headers ⓘ |
| documentSeries |
RFC series
ⓘ
linked to:
RFCs
|
| format | plain text ⓘ |
| historicalRole | foundational specification for modern email message structure ⓘ |
| influenced |
MIME message format
ⓘ
linked to:
MIME
RFC 822 ⓘ modern Internet email standards ⓘ |
| language | English ⓘ |
| medium | electronic document ⓘ |
| networkContext | ARPANET ⓘ |
| predecessorOf | RFC 822 ⓘ |
| publishedBy |
Internet Engineering community
ⓘ
Network Working Group ⓘ |
| purpose |
to provide a uniform structure for electronic mail messages
ⓘ
to standardize the format of ARPA network text messages ⓘ |
| relatedTo |
Internet email architecture
ⓘ
RFC 822 ⓘ |
| replacedBy | RFC 822 ⓘ |
| specifies |
header fields for ARPA network text messages
ⓘ
overall message structure for email ⓘ syntax rules for message headers ⓘ |
| standardType | early Internet standard ⓘ |
| status | historic ⓘ |
| title | Standard for the Format of ARPA Network Text Messages ⓘ |
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 733 Description of subject: RFC 733 is an early Internet standard that defined the format for ARPA network text messages, serving as a foundational specification for modern email message structure.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.