Triple

T5554107
Position Surface form Disambiguated ID Type / Status
Subject Takri script E145594 entity
Predicate relatedScript P37 FINISHED
Object Gurmukhi E12238 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: Gurmukhi | Statement: [Takri script, relatedScript, Gurmukhi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gurmukhi
Context triple: [Takri script, relatedScript, Gurmukhi]
  • A. Gurmukhi chosen
    Gurmukhi is an Indic writing system primarily used for the Punjabi language and for recording Sikh religious scriptures.
  • B. Gujarati script
    The Gujarati script is an abugida used primarily to write the Gujarati language and related Indo-Aryan languages, derived from the Devanagari script and characterized by the absence of the horizontal headline.
  • C. Shahmukhi script
    Shahmukhi script is a Perso-Arabic–based writing system primarily used for writing the Punjabi language in Pakistan.
  • D. Sant Bhasha
    Sant Bhasha is a historical North Indian devotional literary language used in Sikh and related spiritual poetry, written in the Gurmukhi script.
  • E. Dogri
    Dogri is an Indo-Aryan language spoken primarily in the Jammu region of India and surrounding areas, recognized as one of the official languages of India.
  • 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_69c008fcaf788190bafa02a1917ee73b completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c01ff9c9c48190b5e587d58c6515d8 completed March 22, 2026, 4:59 p.m.
NED1 Entity disambiguation (via context triple) batch_69c04cfc6f808190a39c607f61dcfa32 completed March 22, 2026, 8:11 p.m.
Created at: March 22, 2026, 3:36 p.m.