RFC 868
E184121
RFC 868 is an Internet standard that specifies the Time Protocol, a simple service for transmitting the time over a network.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 868 canonical | 3 |
How this entity was disambiguated
This entity first appeared as the object of triple T1631610 — 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 868 Context triple: [RFC 854, relatedRFC, RFC 868]
-
A.
RFC 768
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.
-
B.
RFC 883
RFC 883 was an early Internet standard that originally specified the Domain Name System (DNS) before being superseded by later DNS specifications.
-
C.
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.
-
D.
RFC 855
RFC 855 is an Internet standards document that specifies the Telnet protocol’s options and mechanisms for remote terminal communication over TCP/IP networks.
-
E.
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.
- 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 868 Target entity description: RFC 868 is an Internet standard that specifies the Time Protocol, a simple service for transmitting the time over a network.
-
A.
RFC 768
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.
-
B.
RFC 883
RFC 883 was an early Internet standard that originally specified the Domain Name System (DNS) before being superseded by later DNS specifications.
-
C.
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.
-
D.
RFC 855
RFC 855 is an Internet standards document that specifies the Telnet protocol’s options and mechanisms for remote terminal communication over TCP/IP networks.
-
E.
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.
- F. None of above. chosen
Statements (40)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| category | Internet protocol ⓘ |
| complexity | simple ⓘ |
| connectionModel | client-server ⓘ |
| definedIn | Time Protocol specification ⓘ |
| defines | simple time service over a network ⓘ |
| documentSeries | RFC ⓘ |
| field |
Internet engineering
ⓘ
computer networking ⓘ |
| intendedUse | synchronize clocks of computers on a network ⓘ |
| language | English ⓘ |
| networkLayerDependency | IP ⓘ |
| obsoletedBy | Network Time Protocol ⓘ |
| portAssignmentAuthority | IANA ⓘ |
| protocolNumber | 868 ⓘ |
| protocolType | application-layer protocol ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
Internet Society ⓘ |
| relation | predecessor of modern time synchronization protocols ⓘ |
| requestModel | no payload request ⓘ |
| responseModel | single 32-bit time value ⓘ |
| securityConsiderations |
no authentication
ⓘ
vulnerable to spoofing ⓘ |
| serviceType |
time distribution
ⓘ
time synchronization ⓘ |
| specifies | Time Protocol ⓘ |
| standardizes | format of time value over TCP or UDP ⓘ |
| status | Historic ⓘ |
| supersededBy |
NTP
ⓘ
linked to:
Network Time Protocol
|
| tcpPort | 37 ⓘ |
| timeEpoch | 1900-01-01 00:00:00 UTC ⓘ |
| timeRepresentation | 32-bit unsigned integer ⓘ |
| timeUnit | seconds since 1900-01-01 00:00:00 UTC ⓘ |
| title | Time Protocol ⓘ |
| udpPort | 37 ⓘ |
| useCase |
legacy time services
ⓘ
simple embedded systems ⓘ |
| usesTransportProtocol |
TCP
ⓘ
linked to:
Transmission Control Protocol
UDP ⓘ |
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 868 Description of subject: RFC 868 is an Internet standard that specifies the Time Protocol, a simple service for transmitting the time over a network.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.