Triple

T9052004
Position Surface form Disambiguated ID Type / Status
Subject Unicode 3.0 E216905 entity
Predicate follows P134 FINISHED
Object Unicode 2.1 E593925 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 2.1 | Statement: [Unicode 3.0, follows, Unicode 2.1]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Unicode 2.1
Context triple: [Unicode 3.0, follows, Unicode 2.1]
  • A. Unicode 2.0 chosen
    Unicode 2.0 is a major early version of the Unicode Standard that significantly expanded the character repertoire and refined the encoding model for global text representation.
  • B. Unicode 1.0
    Unicode 1.0 was the first published version of the Unicode standard, establishing a unified character encoding system that laid the foundation for modern multilingual text representation in computing.
  • C. Unicode 1.1
    Unicode 1.1 is an early version of the Unicode Standard that expanded character coverage by adding support for additional writing systems and symbols beyond the initial release.
  • D. Unicode 4.1
    Unicode 4.1 is a version of the Unicode Standard released in 2005 that expanded character coverage and refined existing scripts, including support for additional writing systems and symbols.
  • E. Unicode 3.1
    Unicode 3.1 is a version of the Unicode Standard that significantly expanded character coverage, particularly for East Asian scripts and historic writing 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_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.