RFC 768
E121262
RFC 768 is the Internet standard that defines the User Datagram Protocol (UDP), a core transport-layer protocol used for low-latency, connectionless data transmission.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 768 canonical | 3 |
How this entity was disambiguated
This entity first appeared as the object of triple T1054621 — 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 768 Context triple: [Jon Postel, notableWork, RFC 768]
-
A.
RFC 791
RFC 791 is the foundational Internet standard that specifies the design, structure, and operation of the Internet Protocol version 4 (IPv4).
-
B.
RFC 793
RFC 793 is the foundational Internet standard that defines the Transmission Control Protocol (TCP), specifying how reliable, ordered, and error-checked data transmission works between hosts on an IP network.
-
C.
RFC 826
RFC 826 is the Internet standard document that specifies the Address Resolution Protocol (ARP), which maps IP addresses to physical hardware addresses on local networks.
-
D.
RFC 792
RFC 792 is the Internet standard document that specifies the Internet Control Message Protocol (ICMP), which is used for network diagnostics and error reporting in IP networks.
-
E.
RFC 882
RFC 882 was an early Internet standard that originally specified the Domain Name System (DNS) protocol before being superseded by later RFCs such as RFC 1035.
- 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 768 Target entity description: RFC 768 is the Internet standard that defines the User Datagram Protocol (UDP), a core transport-layer protocol used for low-latency, connectionless data transmission.
-
A.
RFC 791
RFC 791 is the foundational Internet standard that specifies the design, structure, and operation of the Internet Protocol version 4 (IPv4).
-
B.
RFC 793
RFC 793 is the foundational Internet standard that defines the Transmission Control Protocol (TCP), specifying how reliable, ordered, and error-checked data transmission works between hosts on an IP network.
-
C.
RFC 826
RFC 826 is the Internet standard document that specifies the Address Resolution Protocol (ARP), which maps IP addresses to physical hardware addresses on local networks.
-
D.
RFC 792
RFC 792 is the Internet standard document that specifies the Internet Control Message Protocol (ICMP), which is used for network diagnostics and error reporting in IP networks.
-
E.
RFC 882
RFC 882 was an early Internet standard that originally specified the Domain Name System (DNS) protocol before being superseded by later RFCs such as RFC 1035.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| abbreviation | UDP ⓘ |
| area |
Internet protocols
ⓘ
computer networking ⓘ |
| category | Standards Track RFC ⓘ |
| checksumCoverage |
UDP data payload
ⓘ
UDP ⓘ
surface form:
UDP header
|
| checksumUsage |
mandatory in IPv6
ⓘ
optional in IPv4 ⓘ |
| defines |
UDP
ⓘ
surface form:
User Datagram Protocol
|
| definesProtocolFor | application-level protocols ⓘ |
| focusesOn | low-latency data transmission ⓘ |
| hasPortNumberSpace | 16-bit UDP port numbers ⓘ |
| language | English ⓘ |
| partOf |
TCP/IP
ⓘ
surface form:
Internet protocol suite
|
| protocolLayer | transport layer ⓘ |
| protocolType |
connectionless
ⓘ
datagram-oriented ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ Internet Society ⓘ |
| relatedTo |
IPv4
ⓘ
Internet Protocol ⓘ UDP ⓘ
surface form:
TCP
Transmission Control Protocol ⓘ |
| specifies |
UDP checksum field
ⓘ
UDP destination port field ⓘ UDP length field ⓘ UDP source port field ⓘ |
| standardizes |
UDP checksum calculation
ⓘ
UDP header format ⓘ UDP port number usage ⓘ |
| title |
UDP
ⓘ
surface form:
User Datagram Protocol
|
| transportService |
best-effort delivery
ⓘ
no congestion control ⓘ no connection establishment ⓘ no flow control ⓘ unreliable delivery ⓘ |
| usedBy |
DHCP
ⓘ
Domain Name System ⓘ
surface form:
DNS
Domain Name System ⓘ DHCP ⓘ
surface form:
Dynamic Host Configuration Protocol
RIP ⓘ Routing Information Protocol ⓘ SNMP ⓘ SNMP ⓘ
surface form:
Simple Network Management Protocol
real-time applications ⓘ streaming media applications ⓘ |
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 768 Description of subject: RFC 768 is the Internet standard that defines the User Datagram Protocol (UDP), a core transport-layer protocol used for low-latency, connectionless data transmission.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.