Triple

T9052069
Position Surface form Disambiguated ID Type / Status
Subject Unicode 3.0 E216905 entity
Predicate definesEncodingForm P66343 FINISHED
Object UTF-16 E453728 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: UTF-16 | Statement: [Unicode 3.0, definesEncodingForm, UTF-16]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: UTF-16
Context triple: [Unicode 3.0, definesEncodingForm, UTF-16]
  • A. UTF-16 chosen
    UTF-16 is a variable-length character encoding for Unicode that represents most common characters in one 16-bit code unit and others, including supplementary characters, in pairs of 16-bit code units.
  • B. UTF-8
    UTF-8 is a widely used variable-length character encoding standard for Unicode that efficiently represents text in most of the world's writing systems while maintaining backward compatibility with ASCII.
  • C. UTF-32
    UTF-32 is a fixed-length Unicode character encoding that represents each code point using 32 bits, providing simple indexing at the cost of higher memory usage.
  • D. UCS-2
    UCS-2 is a fixed-length 16-bit character encoding that represents Unicode code points in the Basic Multilingual Plane, preceding and largely superseded by UTF-16.
  • E. Unicode
    Unicode is a universal character encoding standard that assigns unique code points to virtually all written scripts, symbols, and emojis used in modern computing.
  • 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_69ca83d362e88190ae44b4e4dc194209 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cc7a700de48190aa9f61d850e01cbd completed April 1, 2026, 1:52 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfebd1450c819092dccae2c48b100d completed April 3, 2026, 4:33 p.m.
Created at: March 30, 2026, 7:10 p.m.