RFC 9113
E8576
RFC 9113 is the Internet standards document that specifies the HTTP/2 protocol, defining its framing, semantics, and operational behavior on the web.
All labels observed (1)
| Label | Occurrences |
|---|---|
| RFC 9113 canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T53992 — 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 9113 Context triple: [HTTP, definedIn, RFC 9113]
-
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.
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.
-
D.
RFC 8446
RFC 8446 is the Internet standard that specifies TLS 1.3, a major revision of the Transport Layer Security protocol focused on improved security and performance for encrypted communications.
-
E.
RFC 4252
RFC 4252 is an Internet standard that specifies the authentication protocol used by Secure Shell (SSH) for secure remote login and other network services.
- 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 9113 Target entity description: RFC 9113 is the Internet standards document that specifies the HTTP/2 protocol, defining its framing, semantics, and operational behavior on the web.
-
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.
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.
-
D.
RFC 8446
RFC 8446 is the Internet standard that specifies TLS 1.3, a major revision of the Transport Layer Security protocol focused on improved security and performance for encrypted communications.
-
E.
RFC 4252
RFC 4252 is an Internet standard that specifies the authentication protocol used by Secure Shell (SSH) for secure remote login and other network services.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
IETF standard
ⓘ
Internet standard ⓘ Request for Comments document ⓘ |
| abbreviation |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| area | Applications and Real-Time Area ⓘ |
| category | Standards Track ⓘ |
| defines |
HTTP/2
ⓘ
surface form:
HTTP/2 framing layer
HTTP/2 operational behavior ⓘ HTTP/2 semantics ⓘ |
| definesConcept |
HTTP/2 GOAWAY behavior
ⓘ
HTTP/2 HPACK usage ⓘ HTTP/2 SETTINGS parameters ⓘ HTTP/2 SETTINGS synchronization ⓘ HTTP/2 SETTINGS_ENABLE_PUSH ⓘ HTTP/2 connection error vs stream error ⓘ HTTP/2 connection management ⓘ HTTP/2 connection preface ⓘ HTTP/2 connection reuse ⓘ HTTP/2 error codes ⓘ HTTP/2 error handling ⓘ HTTP/2 flow control ⓘ HTTP/2 flow-control window ⓘ HTTP/2 frame size limits ⓘ HTTP/2 frame types ⓘ HTTP/2 frames ⓘ HTTP/2 ⓘ
surface form:
HTTP/2 graceful shutdown
HTTP/2 header compression ⓘ HTTP/2 header compression context ⓘ HTTP/2 header fields handling ⓘ HTTP/2 multiplexing ⓘ HTTP/2 prioritization ⓘ HTTP/2 push promise handling ⓘ HTTP/2 reserved stream identifiers ⓘ HTTP/2 security considerations ⓘ HTTP/2 ⓘ
surface form:
HTTP/2 server push
HTTP/2 stream dependencies ⓘ HTTP/2 stream prioritization tree ⓘ HTTP/2 ⓘ
surface form:
HTTP/2 stream states
HTTP/2 streams ⓘ |
| obsoletes |
HTTP/2
ⓘ
surface form:
RFC 7540
|
| protocolLayer | Application layer ⓘ |
| relatedProtocol |
HTTP/1.1
ⓘ
HTTP/3 ⓘ |
| specifiesProtocol | HTTP/2 ⓘ |
| standardsBody | Internet Engineering Task Force ⓘ |
| status | Internet Standard ⓘ |
| stream | IETF Stream ⓘ |
| title | HTTP/2 ⓘ |
| updates | HTTP protocol specification ⓘ |
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 9113 Description of subject: RFC 9113 is the Internet standards document that specifies the HTTP/2 protocol, defining its framing, semantics, and operational behavior on the web.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.