Triple

T6418926
Position Surface form Disambiguated ID Type / Status
Subject Unicode Standard Annexes E127895 entity
Predicate relatedTo P37 FINISHED
Object Unicode Technical Standards E453704 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 Standards | Statement: [Unicode Standard Annexes, relatedTo, Unicode Technical Standards]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Unicode Technical Standards
Context triple: [Unicode Standard Annexes, relatedTo, Unicode Technical Standards]
  • A. 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.
  • 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 Reports chosen
    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.
  • D. Unicode Core Specification
    The Unicode Core Specification is the primary technical standard that defines the Unicode character set, its encoding model, and the fundamental rules for representing and processing text in modern computing systems.
  • E. 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.
  • 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.