HTTP/1.1
E8577
HTTP/1.1 is a widely used version of the Hypertext Transfer Protocol that introduced persistent connections, chunked transfer encoding, and improved caching mechanisms for web communication.
All labels observed (9)
How this entity was disambiguated
This entity first appeared as the object of triple T54027 — 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/1.1 Context triple: [HTTP/2, successorOf, HTTP/1.1]
-
A.
HTTP
HTTP (Hypertext Transfer Protocol) is the foundational application-layer protocol used for transmitting web pages and other resources across the World Wide Web.
-
B.
HTTP/2
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.
-
C.
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.
-
D.
WorldWideWeb (web browser)
WorldWideWeb was the first web browser and editor, created in 1990 as the original client for navigating and editing content on the World Wide Web.
-
E.
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.
- 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/1.1 Target entity description: HTTP/1.1 is a widely used version of the Hypertext Transfer Protocol that introduced persistent connections, chunked transfer encoding, and improved caching mechanisms for web communication.
-
A.
HTTP
HTTP (Hypertext Transfer Protocol) is the foundational application-layer protocol used for transmitting web pages and other resources across the World Wide Web.
-
B.
HTTP/2
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.
-
C.
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.
-
D.
WorldWideWeb (web browser)
WorldWideWeb was the first web browser and editor, created in 1990 as the original client for navigating and editing content on the World Wide Web.
-
E.
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.
- F. None of above. chosen
Statements (56)
| Predicate | Object |
|---|---|
| instanceOf |
HTTP protocol version
ⓘ
application layer protocol ⓘ |
| backwardCompatibleWith | HTTP/1.0 ⓘ |
| coexistsWith |
HTTP/2
ⓘ
HTTP/3 ⓘ |
| defaultPort |
443
ⓘ
80 ⓘ |
| definedIn |
RFC 2068
ⓘ
RFC 2068 ⓘ
surface form:
RFC 2616
RFC 7230 ⓘ RFC 7231 ⓘ RFC 7232 ⓘ RFC 7233 ⓘ RFC 7234 ⓘ RFC 7235 ⓘ |
| enables |
more efficient use of TCP connections
ⓘ
virtual hosting ⓘ |
| follows | HTTP/1.0 ⓘ |
| hasVersionToken | HTTP/1.1 ⓘ |
| improvesOver |
HTTP/1.0 caching behavior
ⓘ
HTTP/1.0 connection reuse ⓘ |
| introducesHeader |
Accept-Ranges
ⓘ
Age ⓘ Cache-Control ⓘ Connection ⓘ ETag ⓘ Expect ⓘ Host ⓘ If-Match ⓘ If-Modified-Since ⓘ If-None-Match ⓘ If-Range ⓘ If-Unmodified-Since ⓘ Pragma ⓘ Range ⓘ TE ⓘ Trailer ⓘ Transfer-Encoding ⓘ Upgrade ⓘ Via ⓘ Warning ⓘ |
| partOf |
HTTP
ⓘ
surface form:
Hypertext Transfer Protocol
|
| standardizedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| status | widely deployed ⓘ |
| supportsFeature |
cache control directives
ⓘ
chunked transfer encoding ⓘ conditional requests ⓘ connection management headers ⓘ content negotiation ⓘ host header for virtual hosting ⓘ improved caching mechanisms ⓘ persistent connections ⓘ pipelining ⓘ range requests ⓘ transfer codings ⓘ |
| uses |
Transmission Control Protocol
ⓘ
surface form:
TCP
|
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/1.1 Description of subject: HTTP/1.1 is a widely used version of the Hypertext Transfer Protocol that introduced persistent connections, chunked transfer encoding, and improved caching mechanisms for web communication.
Referenced by (32)
Full triples — surface form annotated when it differs from this entity's canonical label.
subject surface form:
HTTP/2
this entity surface form:
HTTP/1.1 semantics
this entity surface form:
HTTP/1.1 specification
subject surface form:
Location header
this entity surface form:
HTTP/1.1 specification