Triple

T23477905
Position Surface form Disambiguated ID Type / Status
Subject Dhillon E570319 entity
Predicate scriptUsed P2367 FINISHED
Object Gurmukhi NE NERFINISHED

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: [Dhillon, scriptUsed, Gurmukhi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gurmukhi
Context triple: [Dhillon, scriptUsed, 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. Syloti Nagri
    Syloti Nagri is an Indic script historically used to write the Sylheti language, primarily in the Sylhet region of present-day Bangladesh and India.
  • D. Gaddi Dogri
    Gaddi Dogri is an Indo-Aryan language variety spoken primarily by the Gaddi community in the northern Indian Himalayas.
  • E. 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.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e245af8a88819084f2704f6d265a92 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1a74dbea8819085ca84391039e7f7 completed April 29, 2026, 6:38 a.m.
Created at: April 17, 2026, 6:02 p.m.