Triple

T18295709
Position Surface form Disambiguated ID Type / Status
Subject Ottoman Turkish alphabet E438223 entity
Predicate unicodeRelation P24669 FINISHED
Object represented using Arabic script code points LITERAL 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: represented using Arabic script code points | Statement: [Ottoman Turkish alphabet, unicodeRelation, represented using Arabic script code points]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: unicodeRelation
Context triple: [Ottoman Turkish alphabet, unicodeRelation, represented using Arabic script code points]
  • A. relationshipToUnicode chosen
    Indicates a mapping or association between an entity and its corresponding Unicode representation or code point.
  • B. UnicodePlane
    Indicates that a Unicode code point belongs to a specific Unicode plane (a contiguous range of code points grouped by plane number).
  • C. UnicodeBlock
    Indicates that a character belongs to a specific contiguous range of code points defined as a Unicode block.
  • D. unicodeCodePoint
    Indicates that a character or symbol is associated with a specific Unicode code point value in the Unicode standard.
  • E. hasUnicodeName
    Indicates that an entity is associated with a specific official Unicode name assigned to a character or symbol.
  • F. None of above.

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_69d8b915e3e881909125d760c15d0c29 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e5017783748190905ce4eeadd25841 completed April 19, 2026, 4:23 p.m.
PD Predicate disambiguation batch_69e44fdf43d08190bbcfb6b1fe3cc0ee completed April 19, 2026, 3:45 a.m.
Created at: April 10, 2026, 10:35 a.m.