Triple

T26467452
Position Surface form Disambiguated ID Type / Status
Subject Unicode 13.0 E665804 entity
Predicate definesUnicodeVersionFor P87767 FINISHED
Object Unicode Character Database 13.0.0 NE NERFINISHED

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 Character Database 13.0.0 | Statement: [Unicode 13.0, definesUnicodeVersionFor, Unicode Character Database 13.0.0]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: definesUnicodeVersionFor
Context triple: [Unicode 13.0, definesUnicodeVersionFor, Unicode Character Database 13.0.0]
  • A. UnicodeStandardVersionIntroduced
    Indicates the specific version of the Unicode Standard in which a given character, feature, or property was first introduced.
  • B. definesVersionOf chosen
    Indicates that one entity specifies or establishes the version or variant identity of another entity.
  • C. 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.
  • D. hasUnicodeStandard
    Indicates that something conforms to, is defined by, or is associated with a particular version or aspect of the Unicode standard.
  • E. definesCodePointsFor
    Indicates that one entity specifies or assigns the set of code points used or recognized by another entity.
  • 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_69ee883e812c8190a9b5a9cdb87fee5e completed April 26, 2026, 9:48 p.m.
NER Named-entity recognition batch_69f6d0d46aec819091edf97324d793ac completed May 3, 2026, 4:36 a.m.
PD Predicate disambiguation batch_69f6cfe2183481908ae4e85a59c66f69 completed May 3, 2026, 4:32 a.m.
Created at: April 27, 2026, 12:17 a.m.