Triple

T22585047
Position Surface form Disambiguated ID Type / Status
Subject Unicode bidirectional algorithm E564766 entity
Predicate hasShortName P1354 FINISHED
Object UAX #9 — NE NERFINISHED

How this triple was built (3 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: UAX #9 | Statement: [Unicode bidirectional algorithm, hasShortName, UAX #9]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: UAX #9
Context triple: [Unicode bidirectional algorithm, hasShortName, UAX #9]
  • A. UAX #15
    UAX #15 is the Unicode Standard Annex that defines Unicode Normalization Forms and related algorithms for consistent text representation and comparison.
  • B. CJK Unified Ideographs Extension A
    CJK Unified Ideographs Extension A is a Unicode block that adds additional rare and historic Chinese, Japanese, and Korean characters beyond those included in the main CJK Unified Ideographs block.
  • C. 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.
  • D. Alfabeto Unificado
    Alfabeto Unificado is a standardized writing system proposed for the Mapudungun language to promote consistent spelling and literacy among its speakers.
  • 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. 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: UAX #9
Target entity description: UAX #9 is the Unicode Standard Annex that defines the bidirectional text algorithm used to correctly display mixed left-to-right and right-to-left scripts.
  • A. UAX #15
    UAX #15 is the Unicode Standard Annex that defines Unicode Normalization Forms and related algorithms for consistent text representation and comparison.
  • B. CJK Unified Ideographs Extension A
    CJK Unified Ideographs Extension A is a Unicode block that adds additional rare and historic Chinese, Japanese, and Korean characters beyond those included in the main CJK Unified Ideographs block.
  • C. 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.
  • D. Alfabeto Unificado
    Alfabeto Unificado is a standardized writing system proposed for the Mapudungun language to promote consistent spelling and literacy among its speakers.
  • 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. chosen

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_69e245836014819091b91ed3074742a3 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f1615c18f88190ad4f23639d15f337 completed April 29, 2026, 1:39 a.m.
Created at: April 17, 2026, 2:45 p.m.