Triple

T6442013
Position Surface form Disambiguated ID Type / Status
Subject Supplementary Special-purpose Plane E138246 entity
Predicate utf16Encoding P20982 FINISHED
Object represented as surrogate pairs 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 as surrogate pairs | Statement: [Supplementary Special-purpose Plane, utf16Encoding, represented as surrogate pairs]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: utf16Encoding
Context triple: [Supplementary Special-purpose Plane, utf16Encoding, represented as surrogate pairs]
  • A. encodedInUnicodeSince
    Indicates that a given character or symbol has been included and assigned a code point in the Unicode standard starting from a specific version or time.
  • B. textEncoderType
    Indicates the specific kind or configuration of encoder used to process or represent text in a system or model.
  • C. hasUnicode
    Indicates that an entity is associated with, represented by, or encoded using a specific Unicode character or sequence.
  • D. hasUnicodeStandard
    Indicates that something conforms to, is defined by, or is associated with a particular version or aspect of the Unicode standard.
  • E. codingSystemType chosen
    Indicates the classification or category of coding system used to encode or represent information in a given context.
  • 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_69c008aa61ac8190bc96715ed79fe2d8 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c06989dfb88190b25ff8b2c53f3ced completed March 22, 2026, 10:13 p.m.
PD Predicate disambiguation batch_69c060faaf248190bbdc8ff909c8777a completed March 22, 2026, 9:36 p.m.
Created at: March 22, 2026, 4:46 p.m.