Triple

T22185484
Position Surface form Disambiguated ID Type / Status
Subject UTS #35 E548284 entity
Predicate hasFullName P16 FINISHED
Object Unicode Technical Standard #35 — NE NERFINISHED

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: [UTS #35, hasFullName, Unicode Technical Standard #35]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Unicode Technical Standard #35
Context triple: [UTS #35, hasFullName, 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 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.
  • E. 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.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69e11e3e0c7c8190b30d278845e2497e completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f12aa823888190829368de6db4aa91 completed April 28, 2026, 9:46 p.m.
Created at: April 16, 2026, 8:35 p.m.