RFC 2616
E290849
RFC 2616 is the IETF specification that defined HTTP/1.1, standardizing the core semantics and behavior of the Hypertext Transfer Protocol used on the web.
All labels observed (2)
| Label | Occurrences |
|---|---|
| RFC 2616 canonical | 6 |
| HTTP/1.1 for authoring extensions | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T2703241 — 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 2616 Context triple: [RFC 2068, obsoletedBy, RFC 2616]
-
A.
RFC 2068
RFC 2068 is an early Internet standards document that specifies the HTTP/1.1 protocol, detailing its methods, headers, and overall message structure for web communication.
-
B.
RFC 7231
RFC 7231 is an IETF specification that defined the semantics and content of the HTTP/1.1 protocol, including methods, status codes, and header fields, before being superseded by RFC 9112.
-
C.
RFC 2623
RFC 2623 was an early Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4250.
-
D.
RFC 7230
RFC 7230 is an IETF standard that specifies the core message syntax and routing semantics for the Hypertext Transfer Protocol (HTTP/1.1), including its use over secure transport like HTTPS.
-
E.
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.
- 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 2616 Target entity description: RFC 2616 is the IETF specification that defined HTTP/1.1, standardizing the core semantics and behavior of the Hypertext Transfer Protocol used on the web.
-
A.
RFC 2068
RFC 2068 is an early Internet standards document that specifies the HTTP/1.1 protocol, detailing its methods, headers, and overall message structure for web communication.
-
B.
RFC 7231
RFC 7231 is an IETF specification that defined the semantics and content of the HTTP/1.1 protocol, including methods, status codes, and header fields, before being superseded by RFC 9112.
-
C.
RFC 2623
RFC 2623 was an early Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4250.
-
D.
RFC 7230
RFC 7230 is an IETF standard that specifies the core message syntax and routing semantics for the Hypertext Transfer Protocol (HTTP/1.1), including its use over secure transport like HTTPS.
-
E.
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.
- F. None of above. chosen
Statements (51)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard
ⓘ
Request for Comments document ⓘ |
| appliesTo | World Wide Web ⓘ |
| area | Applications ⓘ |
| category | Standards Track ⓘ |
| defines |
HTTP authentication framework
ⓘ
HTTP caching semantics ⓘ HTTP conditional requests ⓘ HTTP content negotiation ⓘ HTTP header fields ⓘ HTTP methods ⓘ HTTP persistent connections ⓘ HTTP range requests ⓘ
linked to:
HTTP/1.1 Range Requests
HTTP status codes ⓘ HTTP/1.1 message syntax ⓘ HTTP/1.1 semantics ⓘ |
| definesHeaderCategory |
Entity header fields
ⓘ
General header fields ⓘ Request header fields ⓘ Response header fields ⓘ |
| definesMethod |
CONNECT
ⓘ
DELETE ⓘ GET ⓘ HEAD ⓘ OPTIONS ⓘ POST ⓘ PUT ⓘ TRACE ⓘ |
| definesStatusCodeClass |
1xx Informational
ⓘ
2xx Success ⓘ 3xx Redirection ⓘ 4xx Client Error ⓘ 5xx Server Error ⓘ |
| language | English ⓘ |
| obsoletedBy |
RFC 7230
ⓘ
RFC 7231 ⓘ RFC 7232 ⓘ RFC 7233 ⓘ RFC 7234 ⓘ RFC 7235 ⓘ |
| obsoletes | RFC 2068 ⓘ |
| protocolStandardized | HTTP/1.1 ⓘ |
| protocolVersion | 1.1 ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ Internet Society ⓘ |
| rfcNumber | 2616 ⓘ |
| standardizes |
behavior of HTTP/1.1
ⓘ
core semantics of HTTP ⓘ |
| status | Obsoleted ⓘ |
| title |
Hypertext Transfer Protocol – HTTP/1.1
ⓘ
linked to:
HTTP/1.1
|
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 2616 Description of subject: RFC 2616 is the IETF specification that defined HTTP/1.1, standardizing the core semantics and behavior of the Hypertext Transfer Protocol used on the web.
Referenced by (7)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: RFC 2616