Triple

T21139247
Position Surface form Disambiguated ID Type / Status
Subject Sidetic language E520886 entity
Predicate writingSystem P454 FINISHED
Object Sidetic script 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: Sidetic script | Statement: [Sidetic language, writingSystem, Sidetic script]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sidetic script
Context triple: [Sidetic language, writingSystem, Sidetic script]
  • A. Sidetic script chosen
    The Sidetic script is an ancient Anatolian alphabetic writing system used in the city of Side in Pamphylia during the first millennium BCE.
  • B. Tigalari script
    The Tigalari script is a historical South Indian writing system used primarily to write Tulu and Sanskrit, closely related to other southern Brahmic scripts.
  • C. Tirhuta script
    Tirhuta script is a traditional Brahmic writing system historically used for the Maithili language of the Mithila region in India and Nepal.
  • D. Serṭā script
    The Serṭā script is a cursive form of the Syriac alphabet historically used in West Syriac Christian traditions and for writing languages such as Mlahsô.
  • E. Velish script
    The Velish script is a specialized variant of the traditional Hebrew STaM writing style used for sacred Jewish texts such as Torah scrolls, tefillin, and mezuzot.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69e0b50b53048190ae34e8abbe3c5ada completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e7235e389881908813909e05d1413a completed April 21, 2026, 7:12 a.m.
Created at: April 16, 2026, 2:57 p.m.