Triple

T1250815
Position Surface form Disambiguated ID Type / Status
Subject Unicode Technical Report #29 E26869 entity
Predicate defines P264 FINISHED
Object Unicode text segmentation rules E26869 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 text segmentation rules | Statement: [Unicode Technical Report #29, defines, Unicode text segmentation rules]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Unicode text segmentation rules
Context triple: [Unicode Technical Report #29, defines, Unicode text segmentation rules]
  • A. Grapheme_Cluster_Break
    Grapheme_Cluster_Break is a Unicode text segmentation property used to determine how sequences of code points form user-perceived characters (grapheme clusters) for operations like cursor movement and text selection.
  • 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 chosen
    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 Annexes
    Unicode Standard Annexes are supplementary technical reports that define detailed specifications, algorithms, and guidelines extending and clarifying the core Unicode Standard.
  • E. 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.
  • 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_69a49487a9c48190ba9b05348fd1b53f completed March 1, 2026, 7:33 p.m.
NER Named-entity recognition batch_69a4bf84c73c8190bbb14265cd7ab6ae completed March 1, 2026, 10:36 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac997e7e8c8190a9f9d79a8ec1f574 completed March 7, 2026, 9:32 p.m.
Created at: March 1, 2026, 7:47 p.m.