Unicode Technical Report #29
E26869
Unicode Technical Report #29 is the specification that defines how to determine and segment user-perceived text elements (grapheme clusters), words, and sentences in Unicode text.
All labels observed (6)
| Label | Occurrences |
|---|---|
| UAX #29 | 1 |
| Unicode Technical Report #29 canonical | 1 |
| Unicode Technical Report on text processing | 1 |
| Unicode Technical Reports | 1 |
| Unicode Text Segmentation | 1 |
| Unicode text segmentation rules | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T188957 — 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.
Target entity: Unicode Technical Report #29 Context triple: [Unicode, hasTechnicalReport, Unicode Technical Report #29]
-
A.
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.
-
B.
Unicode Character Database
The Unicode Character Database is a comprehensive collection of machine-readable data files that define the properties, classifications, and behaviors of every character encoded in the Unicode Standard.
-
C.
Unicode
Unicode is a universal character encoding standard that assigns unique code points to virtually all written scripts, symbols, and emojis used in modern computing.
-
D.
ISO/IEC 10646
ISO/IEC 10646 is an international standard that defines the Universal Coded Character Set (UCS), a comprehensive repertoire of characters used worldwide and closely aligned with the Unicode Standard.
-
E.
Unicode Scalar Values
Unicode Scalar Values are the set of valid Unicode code points (excluding surrogate code points) that uniquely identify abstract characters in the Unicode standard.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: Unicode Technical Report #29 Target entity description: Unicode Technical Report #29 is the specification that defines how to determine and segment user-perceived text elements (grapheme clusters), words, and sentences in Unicode text.
-
A.
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.
-
B.
Unicode Character Database
The Unicode Character Database is a comprehensive collection of machine-readable data files that define the properties, classifications, and behaviors of every character encoded in the Unicode Standard.
-
C.
Unicode
Unicode is a universal character encoding standard that assigns unique code points to virtually all written scripts, symbols, and emojis used in modern computing.
-
D.
ISO/IEC 10646
ISO/IEC 10646 is an international standard that defines the Universal Coded Character Set (UCS), a comprehensive repertoire of characters used worldwide and closely aligned with the Unicode Standard.
-
E.
Unicode Scalar Values
Unicode Scalar Values are the set of valid Unicode code points (excluding surrogate code points) that uniquely identify abstract characters in the Unicode standard.
- F. None of above. chosen
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf |
Unicode technical report
ⓘ
text segmentation specification ⓘ |
| allows | locale-specific tailoring of segmentation rules ⓘ |
| appliesTo |
Unicode text
ⓘ
all Unicode scripts ⓘ |
| compatibleWith | Unicode Character Database ⓘ |
| defines |
Unicode Technical Report #29
self-linksurface differs
ⓘ
surface form:
Unicode text segmentation rules
grapheme cluster boundaries ⓘ line break interaction with segmentation ⓘ sentence boundaries ⓘ word boundaries ⓘ |
| definesProperty |
Grapheme_Cluster_Break
ⓘ
Line_Break interaction with segmentation ⓘ Sentence_Break ⓘ Word_Break ⓘ |
| hasAbbreviation |
Unicode Technical Report #29
self-linksurface differs
ⓘ
surface form:
UAX #29
UTR #29 ⓘ |
| hasAlternateTitle |
Unicode Standard Annexes
ⓘ
surface form:
Unicode Standard Annex #29
|
| hasScope |
locale-independent default segmentation
ⓘ
user-perceived text elements ⓘ |
| hasStatus |
Unicode Standard Annexes
ⓘ
surface form:
Unicode Standard Annex
|
| hasTitle |
Unicode Technical Report #29
self-linksurface differs
ⓘ
surface form:
Unicode Text Segmentation
|
| intendedFor |
implementers of regular expression engines
ⓘ
implementers of search and indexing systems ⓘ implementers of text editors ⓘ implementers of text rendering systems ⓘ implementers of word processors ⓘ |
| partOf |
Unicode
ⓘ
surface form:
Unicode Standard
|
| provides |
algorithmic rules for grapheme cluster segmentation
ⓘ
algorithmic rules for sentence segmentation ⓘ algorithmic rules for word segmentation ⓘ |
| publishedBy | Unicode Consortium ⓘ |
| references |
Unicode Standard Annexes
ⓘ
surface form:
Unicode Standard Annex #14
Unicode Standard Annexes ⓘ
surface form:
Unicode Standard Annex #15
|
| specifies |
default grapheme cluster boundaries
ⓘ
default sentence boundary rules ⓘ default word boundary rules ⓘ tailorable segmentation rules ⓘ |
| updatedWithEachVersionOf |
Unicode
ⓘ
surface form:
Unicode Standard
|
| usedBy |
operating systems
ⓘ
programming language libraries ⓘ search engines ⓘ text layout engines ⓘ web browsers ⓘ |
| usesConcept |
default sentence boundaries
ⓘ
default word boundaries ⓘ extended grapheme cluster ⓘ legacy grapheme cluster ⓘ |
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.
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.
Subject: Unicode Technical Report #29 Description of subject: Unicode Technical Report #29 is the specification that defines how to determine and segment user-perceived text elements (grapheme clusters), words, and sentences in Unicode text.
Referenced by (6)
Full triples — surface form annotated when it differs from this entity's canonical label.