Triple

T15001812
Position Surface form Disambiguated ID Type / Status
Subject Anand Karaj E374109 entity
Predicate languageUsed P238 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: [Anand Karaj, languageUsed, Gurmukhi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gurmukhi
Context triple: [Anand Karaj, languageUsed, 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_69d85ccc84388190aa151e5173370c8d completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded72fec948190b1c9705538c57976 completed April 15, 2026, 12:09 a.m.
NED1 Entity disambiguation (via context triple) batch_69fe969e2d888190afbb9c8fd8a707c8 completed May 9, 2026, 2:06 a.m.
Created at: April 10, 2026, 2:54 a.m.