Accept-Language
E200846
Accept-Language is an HTTP request header used to indicate the preferred natural languages for the response content.
All labels observed (2)
| Label | Occurrences |
|---|---|
| Accept-Language canonical | 2 |
| HTTP Accept-Language header | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1812633 — 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: Accept-Language Context triple: [RFC 7231, definesHeaderField, Accept-Language]
-
A.
Region and Language
Region and Language is a Windows Control Panel tool that lets users configure system locale, regional formats, and language settings.
-
B.
Langues
Langues were the regional administrative divisions of the Knights Hospitaller, grouping members by their geographic and linguistic origins.
-
C.
ISO 639
ISO 639 is an international standard that defines codes for the representation of names of languages.
-
D.
Carian language
The Carian language is an extinct Anatolian Indo-European language once spoken in ancient Caria in southwestern Anatolia, known primarily from inscriptions and graffiti.
-
E.
Unicode CLDR
Unicode CLDR is a standardized, collaboratively maintained repository of locale data that underpins internationalization and localization features in software and digital platforms worldwide.
- 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: Accept-Language Target entity description: Accept-Language is an HTTP request header used to indicate the preferred natural languages for the response content.
-
A.
Region and Language
Region and Language is a Windows Control Panel tool that lets users configure system locale, regional formats, and language settings.
-
B.
Langues
Langues were the regional administrative divisions of the Knights Hospitaller, grouping members by their geographic and linguistic origins.
-
C.
ISO 639
ISO 639 is an international standard that defines codes for the representation of names of languages.
-
D.
Carian language
The Carian language is an extinct Anatolian Indo-European language once spoken in ancient Caria in southwestern Anatolia, known primarily from inscriptions and graffiti.
-
E.
Unicode CLDR
Unicode CLDR is a standardized, collaboratively maintained repository of locale data that underpins internationalization and localization features in software and digital platforms worldwide.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
HTTP request header field
ⓘ
content negotiation header ⓘ |
| allowsWildcard | * ⓘ |
| belongsTo | request headers ⓘ |
| canAppearIn |
HTTP GET request
ⓘ
HTTP POST request ⓘ other HTTP methods ⓘ |
| canBeOverriddenBy | user preferences in application settings ⓘ |
| category | HTTP header ⓘ |
| clientSets |
HTTP client libraries
ⓘ
mobile applications ⓘ web browsers ⓘ |
| defaultQValue | 1.0 ⓘ |
| definedIn | RFC 9110 ⓘ |
| exampleValue |
Accept-Language: de, en-GB;q=0.7, en;q=0.5
ⓘ
Accept-Language: en-US,en;q=0.9,fr;q=0.8 ⓘ |
| governedBy | IETF HTTP Working Group specifications ⓘ |
| headerName | Accept-Language ⓘ |
| headerType | request header only ⓘ |
| influences |
language of response representation
ⓘ
selection of localized resources ⓘ |
| interpretedBy |
HTTP servers
ⓘ
web applications ⓘ |
| introducedIn | HTTP/1.1 ⓘ |
| languageTagStandard |
BCP 47
ⓘ
linked to:
IETF BCP 47
RFC 5646 ⓘ
linked to:
IETF BCP 47
|
| mayDifferFrom |
system locale
ⓘ
user interface language ⓘ |
| notUsedFor |
specifying character encoding
ⓘ
specifying content type ⓘ |
| partOf | HTTP protocol ⓘ |
| privacyConsideration | may be used for fingerprinting users ⓘ |
| qValueRange | 0.0 to 1.0 ⓘ |
| relatedTo |
Accept
ⓘ
Accept-Charset ⓘ Accept-Encoding ⓘ Content-Language ⓘ |
| replacesSpecification | RFC 7231 ⓘ |
| securityConsideration | can reveal user locale or language preferences ⓘ |
| serverBehaviorIfAbsent | use server default language ⓘ |
| serverBehaviorIfUnmatched | use best available language or default ⓘ |
| supportsParameter |
language-range
ⓘ
q-value ⓘ |
| syntaxPattern | Accept-Language: <language-range>[;q=<weight>] ⓘ |
| usedFor |
HTTP content negotiation
ⓘ
indicating preferred natural languages for response content ⓘ |
| usesConcept |
language range
ⓘ
quality value weighting ⓘ |
| wildcardMeaning | any language is acceptable ⓘ |
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: Accept-Language Description of subject: Accept-Language is an HTTP request header used to indicate the preferred natural languages for the response content.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: Accept-Language