Content-Encoding
E200847
Content-Encoding is an HTTP header that specifies the compression or transformation applied to the body of a message so that recipients know how to decode it.
All labels observed (1)
| Label | Occurrences |
|---|---|
| Content-Encoding canonical | 2 |
How this entity was disambiguated
This entity first appeared as the object of triple T1812635 — 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: Content-Encoding Context triple: [RFC 7231, definesHeaderField, Content-Encoding]
-
A.
Encoding Standard
The Encoding Standard is a WHATWG specification that defines how text is encoded and decoded on the web to ensure consistent character handling across browsers and platforms.
-
B.
Scott encoding
Scott encoding is a method in lambda calculus for representing algebraic data types and their pattern matching behavior using higher-order functions.
-
C.
UTF-8
UTF-8 is a widely used variable-length character encoding standard for Unicode that efficiently represents text in most of the world's writing systems while maintaining backward compatibility with ASCII.
-
D.
MIME
MIME (Multipurpose Internet Mail Extensions) is an internet standard that extends the format of email to support text in character sets beyond ASCII, as well as attachments like images, audio, video, and application files.
-
E.
HPACK
HPACK is the dedicated header compression format used by HTTP/2 to efficiently encode and transmit HTTP header fields while maintaining security and performance.
- 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: Content-Encoding Target entity description: Content-Encoding is an HTTP header that specifies the compression or transformation applied to the body of a message so that recipients know how to decode it.
-
A.
Encoding Standard
The Encoding Standard is a WHATWG specification that defines how text is encoded and decoded on the web to ensure consistent character handling across browsers and platforms.
-
B.
Scott encoding
Scott encoding is a method in lambda calculus for representing algebraic data types and their pattern matching behavior using higher-order functions.
-
C.
UTF-8
UTF-8 is a widely used variable-length character encoding standard for Unicode that efficiently represents text in most of the world's writing systems while maintaining backward compatibility with ASCII.
-
D.
MIME
MIME (Multipurpose Internet Mail Extensions) is an internet standard that extends the format of email to support text in character sets beyond ASCII, as well as attachments like images, audio, video, and application files.
-
E.
HPACK
HPACK is the dedicated header compression format used by HTTP/2 to efficiently encode and transmit HTTP header fields while maintaining security and performance.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf | HTTP header field ⓘ |
| appliesTo |
HTTP message body
ⓘ
HTTP request ⓘ HTTP response ⓘ |
| canAffect | Content-Length value ⓘ |
| caseInsensitive | true ⓘ |
| defaultBehavior | absence means no additional content coding beyond identity ⓘ |
| definedIn |
RFC 7231
ⓘ
RFC 9110 ⓘ |
| distinguishedFrom | Transfer-Encoding which applies to message framing ⓘ |
| example |
Content-Encoding: br
ⓘ
Content-Encoding: deflate ⓘ Content-Encoding: gzip ⓘ Content-Encoding: gzip, br ⓘ |
| governedBy | HTTP content negotiation ⓘ |
| hasCategory | representation header field ⓘ |
| headerName | Content-Encoding ⓘ |
| introducedIn | HTTP/1.0 extensions ⓘ |
| mustNotConflictWith | Transfer-Encoding semantics ⓘ |
| partOf | HTTP protocol ⓘ |
| performanceImpact | reduces bandwidth at cost of CPU for compression and decompression ⓘ |
| processingOrder | codings are listed in the order in which they were applied ⓘ |
| processingRequirement | recipient must decode in reverse order of codings listed ⓘ |
| purpose |
allow recipient to know how to decode the message body
ⓘ
indicate what content codings have been applied to the representation ⓘ |
| redefinedBy | HTTP Semantics specification ⓘ |
| relatedTo |
Accept-Encoding
ⓘ
Content-Length ⓘ Content-Type ⓘ Transfer-Encoding ⓘ |
| requires | recipient support for the indicated content codings ⓘ |
| scope | applies only to the enclosed representation ⓘ |
| securityConsideration | can be involved in compression side-channel attacks ⓘ |
| semantics | describes the content codings applied to the payload representation ⓘ |
| standardizedIn | HTTP/1.1 ⓘ |
| syntax | Content-Encoding: <coding1>, <coding2>, ... ⓘ |
| typicalUse |
compress HTTP responses to reduce payload size
ⓘ
signal that a response body is compressed with gzip ⓘ |
| usedFor |
compression
ⓘ
transformation of message body ⓘ |
| usedWith |
br content coding
ⓘ
compress content coding ⓘ deflate content coding ⓘ gzip content coding ⓘ identity content coding ⓘ |
| valueType | list of content codings ⓘ |
| visibility | intermediaries may add or remove content codings ⓘ |
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: Content-Encoding Description of subject: Content-Encoding is an HTTP header that specifies the compression or transformation applied to the body of a message so that recipients know how to decode it.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.