Triple

T21718421
Position Surface form Disambiguated ID Type / Status
Subject Unicode 6.1 E536089 entity
Predicate hasTechnicalReport P5712 FINISHED
Object Unicode Standard Annex #44 (Unicode Character Database, updated for 6.1) — 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 Standard Annex #44 (Unicode Character Database, updated for 6.1) | Statement: [Unicode 6.1, hasTechnicalReport, Unicode Standard Annex #44 (Unicode Character Database, updated for 6.1)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Unicode Standard Annex #44 (Unicode Character Database, updated for 6.1)
Context triple: [Unicode 6.1, hasTechnicalReport, Unicode Standard Annex #44 (Unicode Character Database, updated for 6.1)]
  • A. 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.
  • B. Unicode Standard Annexes
    Unicode Standard Annexes are supplementary technical reports that define detailed specifications, algorithms, and guidelines extending and clarifying the core Unicode Standard.
  • C. Unicode 6.3
    Unicode 6.3 is a version of the Unicode Standard that introduced additional characters and refinements to support global text processing prior to the release of Unicode 7.0.
  • D. 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.
  • E. Unicode 6.1
    Unicode 6.1 is a version of the Unicode Standard that expanded character support, including the addition of several new scripts and symbols.
  • 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 Standard Annex #44 (Unicode Character Database, updated for 6.1)
Target entity description: Unicode Standard Annex #44 (Unicode Character Database, updated for 6.1) is a technical specification that defines the structure, content, and maintenance rules of the Unicode Character Database for version 6.1 of the Unicode Standard.
  • A. 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.
  • B. Unicode Standard Annexes
    Unicode Standard Annexes are supplementary technical reports that define detailed specifications, algorithms, and guidelines extending and clarifying the core Unicode Standard.
  • C. Unicode 6.3
    Unicode 6.3 is a version of the Unicode Standard that introduced additional characters and refinements to support global text processing prior to the release of Unicode 7.0.
  • D. 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.
  • E. Unicode 6.1
    Unicode 6.1 is a version of the Unicode Standard that expanded character support, including the addition of several new scripts and symbols.
  • 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_69e0c46c6dd88190a595375fa6ebd701 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69efd96cc58081908dda09819041b888 completed April 27, 2026, 9:47 p.m.
Created at: April 16, 2026, 6:47 p.m.