RFC 2068
E59281
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.
All labels observed (2)
How this entity was disambiguated
This entity first appeared as the object of triple T471953 — 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 2068 Context triple: [HTTP/1.1, definedIn, RFC 2068]
-
A.
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.
-
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 7235
RFC 7235 is an IETF specification that defined the HTTP/1.1 authentication framework, including the use of challenge-response mechanisms like Basic and Digest authentication.
-
D.
RFC 7233
RFC 7233 was an HTTP/1.1 specification that defined range requests and partial content delivery mechanisms for HTTP resources.
-
E.
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.
- 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 2068 Target entity description: 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.
-
A.
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.
-
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 7235
RFC 7235 is an IETF specification that defined the HTTP/1.1 authentication framework, including the use of challenge-response mechanisms like Basic and Digest authentication.
-
D.
RFC 7233
RFC 7233 was an HTTP/1.1 specification that defined range requests and partial content delivery mechanisms for HTTP resources.
-
E.
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.
- F. None of above. chosen
Statements (55)
| Predicate | Object |
|---|---|
| instanceOf |
Internet standard document
ⓘ
Request for Comments ⓘ |
| area | Application layer ⓘ |
| category | Standards Track ⓘ |
| defines |
HTTP/1.1 header fields
ⓘ
HTTP/1.1 methods ⓘ HTTP/1.1 request message format ⓘ HTTP/1.1 response message format ⓘ |
| definesHeaderField |
Accept
ⓘ
Accept-Charset ⓘ Accept-Encoding ⓘ Accept-Language ⓘ Authorization ⓘ Cache-Control ⓘ Connection ⓘ Content-Encoding ⓘ Content-Length ⓘ HTTP Content-Type header ⓘ
surface form:
Content-Type
Date ⓘ Host ⓘ If-Modified-Since ⓘ Last-Modified ⓘ |
| definesMethod |
DELETE
ⓘ
GET ⓘ HEAD ⓘ OPTIONS ⓘ POST ⓘ PUT ⓘ TRACE ⓘ |
| networkModelLayer | Application layer of the Internet protocol suite ⓘ |
| obsoletedBy | RFC 2616 ⓘ |
| protocolFamily |
HTTP
ⓘ
surface form:
Hypertext Transfer Protocol
|
| protocolSpecified | HTTP/1.1 ⓘ |
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ Internet Society ⓘ |
| rfcNumber | 2068 ⓘ |
| series |
RFCs
ⓘ
surface form:
Request for Comments
|
| specifies |
HTTP/1.1 authentication framework
ⓘ
HTTP/1.1 caching semantics ⓘ HTTP/1.1 caching validators ⓘ HTTP/1.1 connection management ⓘ HTTP/1.1 content encoding ⓘ HTTP/1.1 content negotiation ⓘ HTTP/1.1 content negotiation using Accept headers ⓘ HTTP/1.1 date and time formats ⓘ HTTP/1.1 header field syntax ⓘ HTTP/1.1 message length determination ⓘ HTTP/1.1 message routing ⓘ HTTP/1.1 message syntax ⓘ HTTP/1.1 persistent connections ⓘ HTTP/1.1 range requests ⓘ HTTP/1.1 status codes ⓘ |
| status | Obsoleted ⓘ |
| title |
HTTP/1.1
ⓘ
surface form:
Hypertext Transfer Protocol – 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 2068 Description of subject: 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.
Referenced by (6)
Full triples — surface form annotated when it differs from this entity's canonical label.