CLDR Technical Committee
E548283
The CLDR Technical Committee is the Unicode Consortium group responsible for developing and maintaining the Common Locale Data Repository, the standard source of locale data used in internationalization and localization.
All labels observed (2)
| Label | Occurrences |
|---|---|
| CLDR Technical Committee canonical | 1 |
| Unicode CLDR committee | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T5795804 — 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: CLDR Technical Committee Context triple: [Unicode CLDR, hasWorkingGroup, CLDR Technical Committee]
-
A.
Unicode Technical Committee
The Unicode Technical Committee is the primary working group within the Unicode Consortium responsible for developing and maintaining the Unicode Standard and related character encoding specifications.
-
B.
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.
-
C.
Unicode Consortium
The Unicode Consortium is a non-profit organization that standardizes the representation of text and symbols in digital systems worldwide through the Unicode Standard.
-
D.
Unicode Technical Standard #35
Unicode Technical Standard #35 is a Unicode Consortium specification that defines the Locale Data Markup Language (LDML) and related mechanisms for internationalization, including formatting of dates, times, numbers, and other locale-sensitive data.
-
E.
Unicode Technical Standard #10
Unicode Technical Standard #10 is the specification that defines the Unicode Collation Algorithm, providing a standardized method for comparing and sorting Unicode text across languages and platforms.
- 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: CLDR Technical Committee Target entity description: The CLDR Technical Committee is the Unicode Consortium group responsible for developing and maintaining the Common Locale Data Repository, the standard source of locale data used in internationalization and localization.
-
A.
Unicode Technical Committee
The Unicode Technical Committee is the primary working group within the Unicode Consortium responsible for developing and maintaining the Unicode Standard and related character encoding specifications.
-
B.
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.
-
C.
Unicode Consortium
The Unicode Consortium is a non-profit organization that standardizes the representation of text and symbols in digital systems worldwide through the Unicode Standard.
-
D.
Unicode Technical Standard #35
Unicode Technical Standard #35 is a Unicode Consortium specification that defines the Locale Data Markup Language (LDML) and related mechanisms for internationalization, including formatting of dates, times, numbers, and other locale-sensitive data.
-
E.
Unicode Technical Standard #10
Unicode Technical Standard #10 is the specification that defines the Unicode Collation Algorithm, providing a standardized method for comparing and sorting Unicode text across languages and platforms.
- F. None of above. chosen
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf |
Unicode Consortium committee
ⓘ
technical committee ⓘ |
| coordinatesWith |
ICU project
NERFINISHED
ⓘ
Unicode Technical Committee NERFINISHED ⓘ W3C Internationalization Working Group NERFINISHED ⓘ |
| defines |
CLDR data stability policies
ⓘ
CLDR versioning policy NERFINISHED ⓘ locale data submission process ⓘ locale data vetting process ⓘ |
| develops | Common Locale Data Repository NERFINISHED ⓘ |
| field |
internationalization
ⓘ
localization ⓘ software globalization ⓘ |
| focusesOn |
backward compatibility of locale data
ⓘ
interoperability of locale data ⓘ standardized locale data ⓘ |
| governsProject | CLDR Survey Tool data collection ⓘ |
| hasParentOrganization | Unicode Consortium NERFINISHED ⓘ |
| maintains | Common Locale Data Repository NERFINISHED ⓘ |
| meets | regularly by teleconference ⓘ |
| oversees |
CLDR data model
ⓘ
CLDR locale coverage levels ⓘ CLDR releases ⓘ |
| partOf | Unicode Consortium NERFINISHED ⓘ |
| produces |
calendar data
ⓘ
collation data ⓘ currency formatting data ⓘ date and time formatting data ⓘ language data ⓘ list formatting data ⓘ locale data ⓘ locale identifiers ⓘ locale inheritance rules ⓘ measurement unit data ⓘ number formatting data ⓘ plural rules ⓘ territory data ⓘ time zone display names ⓘ |
| publishes |
CLDR data files
ⓘ
CLDR specification NERFINISHED ⓘ release notes ⓘ |
| responsibleFor | Common Locale Data Repository NERFINISHED ⓘ |
| shortName | CLDR-TC NERFINISHED ⓘ |
| supports |
global software products
ⓘ
multilingual software ⓘ |
| usesStandard |
BCP 47 language tags
NERFINISHED
ⓘ
Unicode Standard NERFINISHED ⓘ |
| website | https://cldr.unicode.org/ ⓘ |
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: CLDR Technical Committee Description of subject: The CLDR Technical Committee is the Unicode Consortium group responsible for developing and maintaining the Common Locale Data Repository, the standard source of locale data used in internationalization and localization.
Referenced by (2)
Full triples — surface form annotated when it differs from this entity's canonical label.
this entity surface form:
Unicode CLDR committee