Triple

T1222111
Position Surface form Disambiguated ID Type / Status
Subject Gujarati script E26244 entity
Predicate hasUnicodeVersion P23128 FINISHED
Object Unicode 1.1 and later 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: Unicode 1.1 and later | Statement: [Gujarati script, hasUnicodeVersion, Unicode 1.1 and later]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasUnicodeVersion
Context triple: [Gujarati script, hasUnicodeVersion, Unicode 1.1 and later]
  • A. hasUnicode
    Indicates that an entity is associated with, represented by, or encoded using a specific Unicode character or sequence.
  • B. hasUnicodeStatus
    Indicates that a given entity has a particular Unicode-related classification or status (such as assigned, reserved, deprecated, or noncharacter) within the Unicode standard.
  • C. UnicodeStandardVersionIntroduced chosen
    Indicates the specific version of the Unicode Standard in which a given character, feature, or property was first introduced.
  • D. hasUnicodeName
    Indicates that an entity is associated with a specific official Unicode name assigned to a character or symbol.
  • E. hasUnicodeScript
    Indicates that a character or text element belongs to a specific Unicode script category (such as Latin, Cyrillic, or Han).
  • 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_69a49484688c8190a1bf285eb396a8b6 completed March 1, 2026, 7:33 p.m.
NER Named-entity recognition batch_69a4be21a2bc819094b47580d7c5cdf8 completed March 1, 2026, 10:30 p.m.
PD Predicate disambiguation batch_69a4bb644af08190ba25905f20adb01a completed March 1, 2026, 10:19 p.m.
Created at: March 1, 2026, 7:47 p.m.