Triple

T9052002
Position Surface form Disambiguated ID Type / Status
Subject Unicode 3.0 E216905 entity
Predicate partOf P40 FINISHED
Object Unicode Standard E598531 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 | Statement: [Unicode 3.0, partOf, Unicode Standard]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Unicode Standard
Context triple: [Unicode 3.0, partOf, Unicode Standard]
  • A. Unicode Standard chosen
    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 text worldwide.
  • B. Unicode Technical Standards
    Unicode Technical Standards are a collection of specifications that define how text and related data are consistently encoded, represented, and processed across different platforms and languages in the Unicode ecosystem.
  • 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 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.
  • E. Unicode Standard Annex #38
    Unicode Standard Annex #38 is a technical report that defines the Unicode Han Database (Unihan), specifying data fields and properties for East Asian ideographs used in the 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_69ca83d362e88190ae44b4e4dc194209 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cc7a700de48190aa9f61d850e01cbd completed April 1, 2026, 1:52 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfebc90bf88190bbcdab07ca93f569 completed April 3, 2026, 4:33 p.m.
Created at: March 30, 2026, 7:10 p.m.