Triple

T22185470
Position Surface form Disambiguated ID Type / Status
Subject CLDR Technical Committee E548283 entity
Predicate defines P264 FINISHED
Object CLDR versioning policy — 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 versioning policy | Statement: [CLDR Technical Committee, defines, CLDR versioning policy]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: CLDR versioning policy
Context triple: [CLDR Technical Committee, defines, CLDR versioning policy]
  • A. Unicode Standard versions
    Unicode Standard versions are the successive releases of the Unicode character encoding specification that define the repertoire of characters, properties, and rules used for consistent text representation and processing across different platforms and languages.
  • 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 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.
  • D. Semantic Versioning specification
    The Semantic Versioning specification is a widely adopted versioning scheme for software that defines clear rules for incrementing version numbers based on backward-incompatible changes, new features, and bug fixes.
  • E. Unicode 13.0
    Unicode 13.0 is a version of the Unicode Standard that expanded the encoded character repertoire, including support for scripts such as Old Uyghur and various new symbols and emojis.
  • 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.