RFC 7231
E40362
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.
All labels observed (3)
| Label | Occurrences |
|---|---|
| RFC 7231 canonical | 18 |
| HTTP Semantics | 2 |
| HTTP header field semantics | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T306676 — 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 7231 Context triple: [RFC 9112, obsoletes, RFC 7231]
-
A.
RFC 9110
RFC 9110 is an IETF specification that defines the core semantics and architecture of the Hypertext Transfer Protocol (HTTP).
-
B.
RFC 6241
RFC 6241 is the IETF standard that specifies the Network Configuration Protocol (NETCONF) for managing and configuring network devices.
-
C.
RFC 7950
RFC 7950 is the IETF specification that standardizes the YANG 1.1 data modeling language used for modeling configuration and state data in network management protocols.
-
D.
RFC 9112
RFC 9112 is the IETF specification that standardizes the semantics and behavior of HTTP/1.1.
-
E.
RFC 9111
RFC 9111 is an IETF specification that defines HTTP caching semantics, detailing how responses can be stored, reused, and validated to improve web performance and efficiency.
- 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 7231 Target entity description: 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.
-
A.
RFC 9110
RFC 9110 is an IETF specification that defines the core semantics and architecture of the Hypertext Transfer Protocol (HTTP).
-
B.
RFC 6241
RFC 6241 is the IETF standard that specifies the Network Configuration Protocol (NETCONF) for managing and configuring network devices.
-
C.
RFC 7950
RFC 7950 is the IETF specification that standardizes the YANG 1.1 data modeling language used for modeling configuration and state data in network management protocols.
-
D.
RFC 9112
RFC 9112 is the IETF specification that standardizes the semantics and behavior of HTTP/1.1.
-
E.
RFC 9111
RFC 9111 is an IETF specification that defines HTTP caching semantics, detailing how responses can be stored, reused, and validated to improve web performance and efficiency.
- F. None of above. chosen
Statements (67)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
technical standard ⓘ |
| category | Standards Track ⓘ |
| defines |
HTTP header field semantics
ⓘ
HTTP status code semantics ⓘ HTTP/1.1 methods ⓘ HTTP/1.1 ⓘ
surface form:
HTTP/1.1 semantics
content negotiation ⓘ payload semantics ⓘ representation metadata ⓘ |
| definesConcept |
content coding
ⓘ
media type ⓘ payload body ⓘ proactive negotiation ⓘ reactive negotiation ⓘ representation ⓘ selected representation ⓘ |
| definesHeaderField |
Accept
ⓘ
Accept-Charset ⓘ Accept-Encoding ⓘ Accept-Language ⓘ Allow ⓘ Content-Encoding ⓘ Content-Language ⓘ Content-Location ⓘ MIME ⓘ
surface form:
Content-Type
Date ⓘ From ⓘ Location ⓘ Max-Forwards ⓘ Referer ⓘ Retry-After ⓘ Server ⓘ User-Agent ⓘ Vary ⓘ Warning ⓘ |
| definesMethod |
CONNECT
ⓘ
DELETE ⓘ GET ⓘ HEAD ⓘ OPTIONS ⓘ POST ⓘ PUT ⓘ TRACE ⓘ |
| definesStatusCodeClass |
1xx Informational
ⓘ
2xx Success ⓘ 3xx Redirection ⓘ 4xx Client Error ⓘ 5xx Server Error ⓘ |
| focusesOn | HTTP/1.1 ⓘ |
| obsoletedBy |
RFC 9110
ⓘ
RFC 9112 ⓘ |
| obsoletes |
RFC 2068
ⓘ
surface form:
RFC 2616
|
| partOf |
HTTP/1.1
ⓘ
surface form:
HTTP/1.1 specification suite
|
| publishedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
Internet Engineering Task Force ⓘ |
| publishedInSeries |
RFCs
ⓘ
surface form:
Request for Comments
|
| RFCNumber | 7231 ⓘ |
| specifies |
semantics of HTTP header fields
ⓘ
semantics of HTTP requests ⓘ semantics of HTTP responses ⓘ semantics of HTTP status codes ⓘ |
| standardizes |
HTTP content negotiation
ⓘ
character set negotiation in HTTP ⓘ language negotiation in HTTP ⓘ media type handling in HTTP ⓘ |
| title |
RFC 7230
ⓘ
surface form:
Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
|
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 7231 Description of subject: 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.
Referenced by (21)
Full triples — surface form annotated when it differs from this entity's canonical label.
this entity surface form:
HTTP Semantics