RFC 9110
E39861
RFC 9110 is an IETF specification that defines the core semantics and architecture of the Hypertext Transfer Protocol (HTTP).
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 9110 canonical | 15 |
How this entity was disambiguated
This entity first appeared as the object of triple T306700 — 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 9110 Context triple: [RFC 9112, relatedTo, RFC 9110]
-
A.
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.
-
B.
RFC 9112
RFC 9112 is the IETF specification that standardizes the semantics and behavior of HTTP/1.1.
-
C.
RFC 9113
RFC 9113 is the Internet standards document that specifies the HTTP/2 protocol, defining its framing, semantics, and operational behavior on the web.
-
D.
RFC 9114
RFC 9114 is the Internet standard that specifies HTTP/3, the version of the Hypertext Transfer Protocol that runs over the QUIC transport protocol.
-
E.
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.
- 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 9110 Target entity description: RFC 9110 is an IETF specification that defines the core semantics and architecture of the Hypertext Transfer Protocol (HTTP).
-
A.
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.
-
B.
RFC 9112
RFC 9112 is the IETF specification that standardizes the semantics and behavior of HTTP/1.1.
-
C.
RFC 9113
RFC 9113 is the Internet standards document that specifies the HTTP/2 protocol, defining its framing, semantics, and operational behavior on the web.
-
D.
RFC 9114
RFC 9114 is the Internet standard that specifies HTTP/3, the version of the Hypertext Transfer Protocol that runs over the QUIC transport protocol.
-
E.
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.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
IETF Request for Comments
ⓘ
technical specification ⓘ |
| area | Applications and Real-Time Area ⓘ |
| category | Standards Track ⓘ |
| defines |
HTTP caching semantics
ⓘ
HTTP conditional request semantics ⓘ HTTP content negotiation semantics ⓘ HTTP header field semantics ⓘ
linked to:
RFC 7231
HTTP message semantics ⓘ HTTP methods semantics ⓘ HTTP range request semantics ⓘ HTTP status code semantics ⓘ architecture of HTTP ⓘ core semantics of HTTP ⓘ semantics of HTTP content codings ⓘ semantics of HTTP date and time formats ⓘ semantics of HTTP language tags ⓘ semantics of HTTP media types ⓘ semantics of HTTP message framing independent of transport ⓘ semantics of HTTP trailer fields ⓘ semantics of authentication framework in HTTP ⓘ semantics of cacheable methods in HTTP ⓘ semantics of content negotiation using Accept header fields ⓘ semantics of idempotent methods in HTTP ⓘ semantics of representation metadata in HTTP ⓘ semantics of request target and URI handling in HTTP ⓘ semantics of safe methods in HTTP ⓘ semantics of the request-response messaging abstraction in HTTP ⓘ |
| focusesOn | semantics rather than wire format ⓘ |
| obsoletes |
RFC 7231
ⓘ
RFC 7232 ⓘ RFC 7233 ⓘ RFC 7234 ⓘ RFC 7235 ⓘ |
| partOf |
HTTP core specification set
ⓘ
linked to:
RFC 7230
|
| publishedBy | Internet Engineering Task Force ⓘ |
| replaces |
RFC 7231
ⓘ
RFC 7232 ⓘ RFC 7233 ⓘ RFC 7234 ⓘ RFC 7235 ⓘ |
| separatedFrom |
HTTP caching details defined in RFC 9111
ⓘ
HTTP/1.1 message syntax and routing defined in RFC 9112 ⓘ |
| standardizes | semantics common to HTTP/1.1 and HTTP/2 and HTTP/3 ⓘ |
| status | Internet Standard ⓘ |
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| title |
HTTP Semantics
ⓘ
linked to:
RFC 7231
|
| updatesProtocol |
Hypertext Transfer Protocol
ⓘ
linked to:
HTTP
|
| workingGroup | HTTP 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 9110 Description of subject: RFC 9110 is an IETF specification that defines the core semantics and architecture of the Hypertext Transfer Protocol (HTTP).
Referenced by (15)
Full triples — surface form annotated when it differs from this entity's canonical label.