Triple

T13885911
Position Surface form Disambiguated ID Type / Status
Subject Gian Prabodh E333841 entity
Predicate script P505 FINISHED
Object Gurmukhi (in Sikh manuscripts) 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 (in Sikh manuscripts) | Statement: [Gian Prabodh, script, Gurmukhi (in Sikh manuscripts)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gurmukhi (in Sikh manuscripts)
Context triple: [Gian Prabodh, script, Gurmukhi (in Sikh manuscripts)]
  • 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. Shahmukhi script
    Shahmukhi script is a Perso-Arabic–based writing system primarily used for writing the Punjabi language in Pakistan.
  • D. Eastern Nagari script
    The Eastern Nagari script is an abugida used across eastern South Asia, most prominently for writing the Bengali and Assamese languages.
  • E. Nandinagari script
    Nandinagari script is a historical Brahmic script of southern India, primarily used to write Sanskrit and related languages in the Deccan region.
  • 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_69d81c5dd2d48190b7a5fc1e009de936 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de23a101488190bd790b28033d38b9 completed April 14, 2026, 11:23 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7ce71dcd481908f732542dfb1c3e3 completed May 3, 2026, 10:38 p.m.
Created at: April 9, 2026, 10:15 p.m.