Triple

T16400062
Position Surface form Disambiguated ID Type / Status
Subject ਧੁਡੀਕੇ E398286 entity
Predicate usesScript P1587 FINISHED
Object ਗੁਰਮੁਖੀ ਲਿਪੀ 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: ਗੁਰਮੁਖੀ ਲਿਪੀ | Statement: [ਧੁਡੀਕੇ, usesScript, ਗੁਰਮੁਖੀ ਲਿਪੀ]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: ਗੁਰਮੁਖੀ ਲਿਪੀ
Context triple: [ਧੁਡੀਕੇ, usesScript, ਗੁਰਮੁਖੀ ਲਿਪੀ]
  • 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. Prachalit script
    Prachalit script is a historical Brahmic writing system used primarily for the Nepal Bhasa (Newar) language of the Kathmandu Valley.
  • E. Brahmi script
    The Brahmi script is one of the oldest writing systems of the Indian subcontinent, serving as the ancestor of most modern South and Southeast Asian scripts.
  • 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_69d87f2950248190bc8ad9b9bebdc8c8 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e327cea4e481908400b852a5a7032a completed April 18, 2026, 6:42 a.m.
NED1 Entity disambiguation (via context triple) batch_6a00457baed48190b559af7c0ac2711d completed May 10, 2026, 8:44 a.m.
Created at: April 10, 2026, 5:09 a.m.