Triple

T6418895
Position Surface form Disambiguated ID Type / Status
Subject Unicode Standard Annexes E127895 entity
Predicate hasComponent P35 FINISHED
Object Unicode Standard Annex #29 E127895 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 Standard Annex #29 | Statement: [Unicode Standard Annexes, hasComponent, Unicode Standard Annex #29]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Unicode Standard Annex #29
Context triple: [Unicode Standard Annexes, hasComponent, Unicode Standard Annex #29]
  • A. Unicode Standard Annexes chosen
    Unicode Standard Annexes are supplementary technical reports that define detailed specifications, algorithms, and guidelines extending and clarifying the core Unicode Standard.
  • B. 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.
  • 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. 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.
  • E. The Unicode Standard
    The Unicode Standard is a universal character encoding system that assigns unique code points to text and symbols from virtually all writing systems, enabling consistent digital representation and interchange of written language worldwide.
  • 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_69c0083815208190a9b299b8e0640218 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c0690194dc8190b3382bd5f92876b5 completed March 22, 2026, 10:11 p.m.
NED1 Entity disambiguation (via context triple) batch_69c65fc4dc588190ad983fde8969c20f completed March 27, 2026, 10:45 a.m.
Created at: March 22, 2026, 4:42 p.m.