HTTP/2
E6319
HTTP/2 is a major revision of the Hypertext Transfer Protocol that introduced features like multiplexing, header compression, and server push to significantly improve web performance over HTTP/1.1.
All labels observed (11)
| Label | Occurrences |
|---|---|
| HTTP/2 canonical | 20 |
| RFC 7540 | 3 |
| HPACK | 1 |
| HTTP/2 framing layer | 1 |
| HTTP/2 graceful shutdown | 1 |
| HTTP/2 intermediaries | 1 |
| HTTP/2 server push | 1 |
| HTTP/2 stream states | 1 |
| Hypertext Transfer Protocol (httpbis) | 1 |
| Hypertext Transfer Protocol Version 2 | 1 |
| Hypertext Transfer Protocol Version 2 (HTTP/2) | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T54028 — 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: HTTP/2 Context triple: [HTTP/3, successorOf, HTTP/2]
-
A.
HTTP/3
HTTP/3 is the third major version of the Hypertext Transfer Protocol, built on the QUIC transport protocol to provide faster, more reliable, and secure web communication.
-
B.
HTTP
HTTP (Hypertext Transfer Protocol) is the foundational application-layer protocol used for transmitting web pages and other resources across the World Wide Web.
-
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.
Internet Protocol version 6
Internet Protocol version 6 (IPv6) is the modern Internet addressing and routing protocol designed to replace IPv4 by providing a vastly larger address space and improved network efficiency and security features.
-
E.
TLS
TLS (Transport Layer Security) is a cryptographic protocol that secures data transmitted over networks by providing encryption, authentication, and integrity between communicating applications.
- 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: HTTP/2 Target entity description: HTTP/2 is a major revision of the Hypertext Transfer Protocol that introduced features like multiplexing, header compression, and server push to significantly improve web performance over HTTP/1.1.
-
A.
HTTP/3
HTTP/3 is the third major version of the Hypertext Transfer Protocol, built on the QUIC transport protocol to provide faster, more reliable, and secure web communication.
-
B.
HTTP
HTTP (Hypertext Transfer Protocol) is the foundational application-layer protocol used for transmitting web pages and other resources across the World Wide Web.
-
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.
Internet Protocol version 6
Internet Protocol version 6 (IPv6) is the modern Internet addressing and routing protocol designed to replace IPv4 by providing a vastly larger address space and improved network efficiency and security features.
-
E.
TLS
TLS (Transport Layer Security) is a cryptographic protocol that secures data transmitted over networks by providing encryption, authentication, and integrity between communicating applications.
- F. None of above. chosen
Statements (55)
| Predicate | Object |
|---|---|
| instanceOf |
Hypertext Transfer Protocol version
ⓘ
application layer protocol ⓘ network protocol ⓘ |
| backwardsCompatibleWith | HTTP/1.1 semantics ⓘ |
| canBeUsedOver |
TLS
ⓘ
cleartext TCP ⓘ |
| cleartextUpgradeMechanism | HTTP Upgrade header ⓘ |
| compatibleWith |
HTTP URIs
ⓘ
HTTP methods ⓘ HTTP semantics ⓘ HTTP status codes ⓘ |
| defaultPortOverCleartext | 80 ⓘ |
| defaultPortOverTLS | 443 ⓘ |
| definedInRFC |
HTTP/2
self-linksurface differs
ⓘ
surface form:
RFC 7540
RFC 7541 ⓘ |
| doesNotChange |
HTTP authentication semantics
ⓘ
HTTP caching semantics ⓘ HTTP cookies semantics ⓘ URI scheme semantics ⓘ |
| follows | HTTP/1.1 ⓘ |
| headerCompressionAlgorithm | HPACK ⓘ |
| improves | web performance ⓘ |
| influencedBy | SPDY ⓘ |
| layer | application layer ⓘ |
| multiplexingAllows | multiple concurrent streams over a single TCP connection ⓘ |
| negotiatedVia | ALPN ⓘ |
| obsoletedBy | HTTP/3 (for many deployments) ⓘ |
| originatedFrom | SPDY ⓘ |
| partOf |
TCP/IP
ⓘ
surface form:
Internet protocol suite
|
| publicationYear | 2015 ⓘ |
| reduces |
header overhead
ⓘ
latency ⓘ |
| replaces | text-based message framing of HTTP/1.1 ⓘ |
| securityRecommendation | use over TLS ⓘ |
| serverPushAllows | sending resources before client requests them ⓘ |
| standardizedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| status | Proposed Standard ⓘ |
| streamIdentifierType | integer ⓘ |
| successorTo | HTTP/1.1 ⓘ |
| supportsFeature |
binary framing
ⓘ
flow control ⓘ header compression ⓘ multiplexing ⓘ persistent connections ⓘ request pipelining without head-of-line blocking at HTTP layer ⓘ server push ⓘ stream prioritization ⓘ |
| TLSALPNIdentifier | h2 ⓘ |
| transportProtocol |
Transmission Control Protocol
ⓘ
surface form:
TCP
|
| uses | binary framing layer ⓘ |
| usesConcept |
connections
ⓘ
frames ⓘ messages ⓘ streams ⓘ |
| usesHeaderCompressionSpecification |
HTTP/2
self-linksurface differs
ⓘ
surface form:
HPACK
|
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: HTTP/2 Description of subject: HTTP/2 is a major revision of the Hypertext Transfer Protocol that introduced features like multiplexing, header compression, and server push to significantly improve web performance over HTTP/1.1.
Referenced by (32)
Full triples — surface form annotated when it differs from this entity's canonical label.
subject surface form:
HTTP/3
this entity surface form:
RFC 7540
this entity surface form:
HPACK
this entity surface form:
HTTP/2 server push
this entity surface form:
HTTP/2 stream states
this entity surface form:
HTTP/2 graceful shutdown
this entity surface form:
Hypertext Transfer Protocol Version 2 (HTTP/2)
this entity surface form:
Hypertext Transfer Protocol (httpbis)
subject surface form:
ALPN