Triple

T18564539
Position Surface form Disambiguated ID Type / Status
Subject UTF-16 E453728 entity
Predicate usedBy P260 FINISHED
Object JavaScript (UTF-16 code units for strings) — 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: JavaScript (UTF-16 code units for strings) | Statement: [UTF-16, usedBy, JavaScript (UTF-16 code units for strings)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: JavaScript (UTF-16 code units for strings)
Context triple: [UTF-16, usedBy, JavaScript (UTF-16 code units for strings)]
  • A. UTF-16
    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. Punycode
    Punycode is a standardized encoding system that represents Unicode characters using only ASCII characters, enabling internationalized domain names to be used within the traditional DNS infrastructure.
  • D. 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.
  • E. Rhino JavaScript engine
    Rhino JavaScript engine is an open-source JavaScript implementation written in Java that runs on the JVM and is used to execute JavaScript code within Java-based environments.
  • 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: JavaScript (UTF-16 code units for strings)
Target entity description: JavaScript (UTF-16 code units for strings) refers to the language’s internal string representation, where text is stored as sequences of 16-bit code units rather than raw Unicode code points.
  • 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. Punycode
    Punycode is a standardized encoding system that represents Unicode characters using only ASCII characters, enabling internationalized domain names to be used within the traditional DNS infrastructure.
  • D. 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.
  • E. Rhino JavaScript engine
    Rhino JavaScript engine is an open-source JavaScript implementation written in Java that runs on the JVM and is used to execute JavaScript code within Java-based environments.
  • F. None of above.

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_69d8d38974308190a9174430ef256b73 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e53afd8114819093b57d86f8213311 completed April 19, 2026, 8:28 p.m.
Created at: April 10, 2026, 11:42 a.m.