RFC 5905
E234528
RFC 5905 is the Internet standard specification that defines version 4 of the Network Time Protocol (NTP) for synchronizing clocks over packet-switched, variable-latency data networks.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 5905 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T2108328 — 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 5905 Context triple: [Network Time Protocol, definedIn, RFC 5905]
-
A.
RFC 9205
RFC 9205 is an IETF specification that provides guidance and best practices for the use and deployment of HTTP, complementing the core protocol definitions in related HTTP RFCs.
-
B.
RFC 5702
RFC 5702 is an Internet standards document that specifies the use of SHA-2 family hash algorithms with DNSSEC to enhance the security of DNS authentication.
-
C.
RFC 6605
RFC 6605 is an Internet standards document that specifies the use of Elliptic Curve Digital Signature Algorithm (ECDSA) with the Domain Name System Security Extensions (DNSSEC) to provide more efficient cryptographic signing and validation of DNS data.
-
D.
RFC 5155
RFC 5155 is an Internet standards document that specifies the NSEC3 extension to DNSSEC, enhancing DNS security by providing authenticated denial of existence while mitigating zone enumeration.
-
E.
RFC 6052
RFC 6052 is an IETF standard that defines the IPv6 address format for representing IPv4 addresses, forming a core part of NAT64 and IPv4/IPv6 transition mechanisms.
- 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 5905 Target entity description: RFC 5905 is the Internet standard specification that defines version 4 of the Network Time Protocol (NTP) for synchronizing clocks over packet-switched, variable-latency data networks.
-
A.
RFC 9205
RFC 9205 is an IETF specification that provides guidance and best practices for the use and deployment of HTTP, complementing the core protocol definitions in related HTTP RFCs.
-
B.
RFC 5702
RFC 5702 is an Internet standards document that specifies the use of SHA-2 family hash algorithms with DNSSEC to enhance the security of DNS authentication.
-
C.
RFC 6605
RFC 6605 is an Internet standards document that specifies the use of Elliptic Curve Digital Signature Algorithm (ECDSA) with the Domain Name System Security Extensions (DNSSEC) to provide more efficient cryptographic signing and validation of DNS data.
-
D.
RFC 5155
RFC 5155 is an Internet standards document that specifies the NSEC3 extension to DNSSEC, enhancing DNS security by providing authenticated denial of existence while mitigating zone enumeration.
-
E.
RFC 6052
RFC 6052 is an IETF standard that defines the IPv6 address format for representing IPv4 addresses, forming a core part of NAT64 and IPv4/IPv6 transition mechanisms.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments ⓘ |
| appliesTo |
packet‑switched data networks
ⓘ
variable‑latency data networks ⓘ |
| area | Internet Area ⓘ |
| category | Standards Track ⓘ |
| defines |
NTP association modes
ⓘ
NTP broadcast mode ⓘ NTP clock discipline algorithm ⓘ NTP clock filtering algorithms ⓘ NTP clock selection algorithms ⓘ NTP clustering and combining algorithms ⓘ NTP dispersion and delay calculations ⓘ NTP extension field format ⓘ NTP interleaved modes ⓘ NTP kiss‑of‑death packet semantics ⓘ NTP leap indicator semantics ⓘ NTP manycast mode ⓘ NTP on‑wire protocol ⓘ NTP packet header format ⓘ NTP poll interval behavior ⓘ NTP reference clock interface model ⓘ NTP reference identifier semantics ⓘ NTP server and client roles ⓘ NTP state machine ⓘ NTP stratum model ⓘ NTP symmetric active mode ⓘ NTP symmetric passive mode ⓘ NTP system and peer variables ⓘ Network Time Protocol ⓘ
surface form:
NTP timestamp format
|
| definesProtocol | Network Time Protocol ⓘ |
| isObsoletedBy | RFC 9589 ⓘ |
| language | English ⓘ |
| obsoletes |
RFC 1305
ⓘ
RFC 1769 ⓘ RFC 2030 ⓘ RFC 4330 ⓘ |
| protocolVersionDefined | NTPv4 ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| relatedTo |
RFC 5906
ⓘ
RFC 5907 ⓘ |
| specifies |
algorithms for clock synchronization over packet‑switched networks
ⓘ
algorithms for mitigating variable network latency ⓘ |
| standardizes | time synchronization on IP networks ⓘ |
| status | Internet Standard ⓘ |
| stream | IETF Stream ⓘ |
| title |
Network Time Protocol
ⓘ
surface form:
Network Time Protocol Version 4: Protocol and Algorithms Specification
|
| workingGroup |
Network Time Protocol
ⓘ
surface form:
Network Time Protocol Working Group
|
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 5905 Description of subject: RFC 5905 is the Internet standard specification that defines version 4 of the Network Time Protocol (NTP) for synchronizing clocks over packet-switched, variable-latency data networks.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.