Triple

T1745458
Position Surface form Disambiguated ID Type / Status
Subject Arabic alphabet E38326 entity
Predicate usedFor P98 FINISHED
Object Kashmiri language E147793 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: Kashmiri language | Statement: [Arabic alphabet, usedFor, Kashmiri language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kashmiri language
Context triple: [Arabic alphabet, usedFor, Kashmiri language]
  • A. Kashmiri language chosen
    Kashmiri language is an Indo-Aryan language spoken primarily in the Kashmir Valley, written in multiple scripts including a Perso-Arabic–based Nastaʿlīq script.
  • B. 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.
  • C. Punjabi language
    Punjabi language is an Indo-Aryan language widely spoken in the Punjab region of India and Pakistan and among large diaspora communities worldwide.
  • D. Garhwali
    Garhwali is an Indo-Aryan language spoken primarily in the Garhwal region of the Indian state of Uttarakhand.
  • E. Sant Bhasha
    Sant Bhasha is a historical North Indian devotional literary language used in Sikh and related spiritual poetry, written in the Gurmukhi script.
  • 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_69a8862b01a48190ab47209063af82d9 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69aa63e93f3481909f61d581f7a5bdfa completed March 6, 2026, 5:19 a.m.
NED1 Entity disambiguation (via context triple) batch_69ada0de0ff08190bb7758e3ba32de80 completed March 8, 2026, 4:16 p.m.
Created at: March 4, 2026, 7:31 p.m.