RFC 9112
E6318
RFC 9112 is the IETF specification that standardizes the semantics and behavior of HTTP/1.1.
All labels observed (2)
How this entity was disambiguated
This entity first appeared as the object of triple T53991 — 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 9112 Context triple: [HTTP, definedIn, RFC 9112]
-
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.
RFCs
RFCs (Requests for Comments) are a series of technical and organizational documents that define and standardize protocols, procedures, and policies for the Internet and related networks.
-
C.
RFC 5246
RFC 5246 is the Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) version 1.2, a widely used protocol for securing communications over computer networks.
-
D.
RFC 4251
RFC 4251 is the core specification that defines the architecture and protocol framework of the Secure Shell (SSH) protocol used for secure remote communication.
-
E.
RFC 1035
RFC 1035 is an Internet standards document that defines the implementation details, message formats, and operational procedures for the Domain Name System (DNS).
- 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 9112 Target entity description: RFC 9112 is the IETF specification that standardizes the semantics and behavior of HTTP/1.1.
-
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.
RFCs
RFCs (Requests for Comments) are a series of technical and organizational documents that define and standardize protocols, procedures, and policies for the Internet and related networks.
-
C.
RFC 5246
RFC 5246 is the Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) version 1.2, a widely used protocol for securing communications over computer networks.
-
D.
RFC 4251
RFC 4251 is the core specification that defines the architecture and protocol framework of the Secure Shell (SSH) protocol used for secure remote communication.
-
E.
RFC 1035
RFC 1035 is an Internet standards document that defines the implementation details, message formats, and operational procedures for the Domain Name System (DNS).
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
HTTP specification
ⓘ
Internet standard ⓘ Request for Comments ⓘ |
| area | Applications and Real-Time ⓘ |
| category | Standards Track ⓘ |
| defines |
ABNF for HTTP/1.1 message syntax
ⓘ
HTTP/1.1 connection management ⓘ HTTP/1.1 header field rules ⓘ HTTP/1.1 message framing ⓘ HTTP/1.1 message syntax ⓘ HTTP/1.1 request semantics ⓘ
linked to:
HTTP/1.1
HTTP/1.1 response semantics ⓘ requirements for HTTP/1.1 clients ⓘ requirements for HTTP/1.1 intermediaries ⓘ requirements for HTTP/1.1 servers ⓘ |
| fullTitle | HTTP/1.1 ⓘ |
| language | English ⓘ |
| obsoletes |
RFC 7230
ⓘ
linked to:
RFC 9112
RFC 7231 ⓘ RFC 7232 ⓘ RFC 7233 ⓘ RFC 7234 ⓘ RFC 7235 ⓘ |
| partOf | HTTP core specifications ⓘ |
| protocol |
Hypertext Transfer Protocol
ⓘ
linked to:
HTTP
|
| protocolVersion | HTTP/1.1 ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
Internet Engineering Task Force ⓘ |
| relatedTo |
RFC 9110
ⓘ
RFC 9111 ⓘ RFC 9113 ⓘ RFC 9205 ⓘ |
| specifies |
HTTP/1.1 caching interaction at message level
ⓘ
HTTP/1.1 chunked transfer coding ⓘ HTTP/1.1 connection header handling ⓘ HTTP/1.1 connection reuse ⓘ HTTP/1.1 header field processing ⓘ HTTP/1.1 intermediaries behavior ⓘ HTTP/1.1 message body length determination ⓘ HTTP/1.1 message parsing requirements ⓘ
linked to:
HTTP/1.1
HTTP/1.1 message routing rules ⓘ HTTP/1.1 persistent connections ⓘ HTTP/1.1 transfer codings ⓘ HTTP/1.1 upgrade mechanism ⓘ |
| standardizes |
HTTP/1.1 behavior
ⓘ
HTTP/1.1 semantics ⓘ
linked to:
HTTP/1.1
|
| status | Internet Standard ⓘ |
| stream |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| title | 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 9112 Description of subject: RFC 9112 is the IETF specification that standardizes the semantics and behavior of HTTP/1.1.
Referenced by (7)
Full triples — surface form annotated when it differs from this entity's canonical label.