Triple

T22050232
Position Surface form Disambiguated ID Type / Status
Subject Tangut Components E544862 entity
Predicate proposalDocument P14218 FINISHED
Object Unicode Tangut encoding proposals — 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: Unicode Tangut encoding proposals | Statement: [Tangut Components, proposalDocument, Unicode Tangut encoding proposals]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Unicode Tangut encoding proposals
Context triple: [Tangut Components, proposalDocument, Unicode Tangut encoding proposals]
  • A. Tangut script
    The Tangut script is a complex, logographic writing system historically used by the Tangut people of the Western Xia dynasty in northwestern China.
  • B. Phags-pa script extensions
    Phags-pa script extensions are additional Unicode characters that expand support for the historic Mongolian and Tibetan-related Phags-pa writing system used during the Yuan dynasty.
  • 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 Consortium
    The Unicode Consortium is a non-profit organization that standardizes the representation of text and symbols in digital systems worldwide through the Unicode Standard.
  • 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: Unicode Tangut encoding proposals
Target entity description: Unicode Tangut encoding proposals are technical documents submitted to the Unicode Consortium that define how the Tangut script and its components should be digitally encoded and standardized.
  • A. Tangut script
    The Tangut script is a complex, logographic writing system historically used by the Tangut people of the Western Xia dynasty in northwestern China.
  • B. Phags-pa script extensions
    Phags-pa script extensions are additional Unicode characters that expand support for the historic Mongolian and Tibetan-related Phags-pa writing system used during the Yuan dynasty.
  • 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 Consortium
    The Unicode Consortium is a non-profit organization that standardizes the representation of text and symbols in digital systems worldwide through the Unicode Standard.
  • 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_69e11e32445c8190ab97089b48a130bb completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f128323fb08190b9592fd08a96cba0 completed April 28, 2026, 9:35 p.m.
Created at: April 16, 2026, 8:26 p.m.