Triple

T16448284
Position Surface form Disambiguated ID Type / Status
Subject Nihang order E399487 entity
Predicate script P505 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: [Nihang order, script, Gurmukhi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gurmukhi
Context triple: [Nihang order, script, Gurmukhi]
  • A. Gurmukhi chosen
    Gurmukhi is an Indic writing system primarily used for the Punjabi language and for recording Sikh religious scriptures.
  • B. Multani script
    Multani script is a historical Brahmic writing system once used primarily for the Multani language and mercantile records in the Multan region of the Indian subcontinent.
  • C. 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.
  • D. Shahmukhi script
    Shahmukhi script is a Perso-Arabic–based writing system primarily used for writing the Punjabi language in Pakistan.
  • 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_69d87f2c6778819080fcfae53be8f12a completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e32cdee44c8190ae0df20c58ff7558 completed April 18, 2026, 7:03 a.m.
NED1 Entity disambiguation (via context triple) batch_6a004f4b738881908f8a205466397f33 completed May 10, 2026, 9:26 a.m.
Created at: April 10, 2026, 5:10 a.m.