RFC 3339
E100895
RFC 3339 is an Internet standard that defines a simplified, unambiguous date and time format commonly used in internet protocols and data interchange.
All labels observed (2)
| Label | Occurrences |
|---|---|
| RFC 2445 (with respect to timestamp format alignment aspects) | 1 |
| RFC 3339 canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T868560 — 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 3339 Context triple: [ISO 8601, influenced, RFC 3339]
-
A.
ISO 8601
ISO 8601 is an international standard that defines a consistent, unambiguous format for representing dates, times, and related data in numeric form.
-
B.
RFC 7233
RFC 7233 was an HTTP/1.1 specification that defined range requests and partial content delivery mechanisms for HTTP resources.
-
C.
RFC 7234
RFC 7234 is an IETF specification that defines HTTP/1.1 caching semantics, including how responses may be stored, reused, and validated by caches.
-
D.
RFC 7232
RFC 7232 is an HTTP/1.1 specification that defines conditional request mechanisms using validators like ETags and Last-Modified to support efficient caching and concurrency control on the web.
-
E.
RFC 9002
RFC 9002 is an IETF standard that specifies the loss detection and congestion control mechanisms for the QUIC transport protocol.
- 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 3339 Target entity description: RFC 3339 is an Internet standard that defines a simplified, unambiguous date and time format commonly used in internet protocols and data interchange.
-
A.
ISO 8601
ISO 8601 is an international standard that defines a consistent, unambiguous format for representing dates, times, and related data in numeric form.
-
B.
RFC 7233
RFC 7233 was an HTTP/1.1 specification that defined range requests and partial content delivery mechanisms for HTTP resources.
-
C.
RFC 7234
RFC 7234 is an IETF specification that defines HTTP/1.1 caching semantics, including how responses may be stored, reused, and validated by caches.
-
D.
RFC 7232
RFC 7232 is an HTTP/1.1 specification that defines conditional request mechanisms using validators like ETags and Last-Modified to support efficient caching and concurrency control on the web.
-
E.
RFC 9002
RFC 9002 is an IETF standard that specifies the loss detection and congestion control mechanisms for the QUIC transport protocol.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard
ⓘ
Request for Comments document ⓘ date and time format specification ⓘ |
| allows | fractional seconds separated by a dot ⓘ |
| basedOn | ISO 8601 ⓘ |
| category | Standards Track ⓘ |
| defines |
ABNF grammar for timestamps
ⓘ
Internet timestamp format ⓘ UTC-based timestamps ⓘ fractional seconds notation ⓘ offset-from-UTC timestamps ⓘ rules for date and time normalization ⓘ rules for leap second representation ⓘ rules for timestamp comparison ⓘ simplified ISO 8601 profile ⓘ time zone offset notation ⓘ timestamp format using +hh:mm or -hh:mm for numeric time zone offsets ⓘ timestamp format using the character T as date-time separator ⓘ timestamp format using the character Z to indicate UTC ⓘ unambiguous date and time representation ⓘ |
| disallows |
ambiguous local times without offset
ⓘ
named time zones ⓘ |
| formatExample |
2006-01-02T15:04:05+07:00
ⓘ
2006-01-02T15:04:05Z ⓘ |
| goal |
interoperability across internet systems
ⓘ
unambiguous machine-readable timestamps ⓘ |
| obsoletes |
RFC 3339
self-linksurface differs
ⓘ
surface form:
RFC 2445 (with respect to timestamp format alignment aspects)
|
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| requires |
2-digit day
ⓘ
2-digit hour ⓘ 2-digit minute ⓘ 2-digit month ⓘ 2-digit second ⓘ 4-digit year ⓘ |
| RFCNumber | 3339 ⓘ |
| status | Internet Standard ⓘ |
| stream |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| timeScale |
Coordinated Universal Time
ⓘ
surface form:
UTC
|
| timeZoneHandling | UTC or fixed numeric offset from UTC ⓘ |
| title | Date and Time on the Internet: Timestamps ⓘ |
| updates |
ISO 8601
ⓘ
surface form:
ISO 8601 (by defining a profile)
|
| useCase |
APIs and web services
ⓘ
JSON data timestamps ⓘ XML data timestamps ⓘ configuration files ⓘ data interchange ⓘ internet protocols ⓘ logging formats ⓘ |
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 3339 Description of subject: RFC 3339 is an Internet standard that defines a simplified, unambiguous date and time format commonly used in internet protocols and data interchange.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.