Triple
T22185473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CLDR Technical Committee |
E548283
|
entity |
| Predicate | publishes |
P80
|
FINISHED |
| Object | CLDR specification |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: CLDR specification | Statement: [CLDR Technical Committee, publishes, CLDR specification]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CLDR specification Context triple: [CLDR Technical Committee, publishes, CLDR specification]
-
A.
Unicode CLDR
chosen
Unicode CLDR is a standardized, collaboratively maintained repository of locale data that underpins internationalization and localization features in software and digital platforms worldwide.
-
B.
CLDR Technical Committee
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.
-
C.
Unicode Core Specification
The Unicode Core Specification is the primary technical standard that defines the Unicode character set, its encoding model, and the fundamental rules for representing and processing text in modern computing systems.
-
D.
Locale Data Markup Language
Locale Data Markup Language (LDML) is an XML-based standard for representing locale-specific data such as date, time, number, and language formats used in internationalization and localization.
-
E.
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.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69e11e3e0c7c8190b30d278845e2497e |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12aa823888190829368de6db4aa91 |
completed | April 28, 2026, 9:46 p.m. |
Created at: April 16, 2026, 8:35 p.m.