Triple

T5795808
Position Surface form Disambiguated ID Type / Status
Subject Unicode CLDR E128504 entity
Predicate documentedIn P309 FINISHED
Object Unicode Technical Standard #35 E158917 NE FINISHED

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: Unicode Technical Standard #35 | Statement: [Unicode CLDR, documentedIn, Unicode Technical Standard #35]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Unicode Technical Standard #35
Context triple: [Unicode CLDR, documentedIn, Unicode Technical Standard #35]
  • A. Unicode Technical Standard #35 chosen
    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.
  • B. 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.
  • C. Unicode Technical Report #29
    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.
  • D. Unicode Technical Reports
    Unicode Technical Reports are supplementary documents published by the Unicode Consortium that provide detailed guidance, algorithms, and clarifications on specific aspects of Unicode beyond what is covered in the core specification.
  • E. Unicode Standard Annexes
    Unicode Standard Annexes are supplementary technical reports that define detailed specifications, algorithms, and guidelines extending and clarifying the core Unicode Standard.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69c00845ca68819081a2ce3ecca577f7 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c02a9304b081909ea004902f4ca569 completed March 22, 2026, 5:44 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0bfb0ea6c819095487404545af9ca completed March 23, 2026, 4:21 a.m.
Created at: March 22, 2026, 3:51 p.m.