Triple

T5315727
Position Surface form Disambiguated ID Type / Status
Subject Hyderabad (Sindh) E119141 entity
Predicate language P15 FINISHED
Object Punjabi E3585 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: Punjabi | Statement: [Hyderabad (Sindh), language, Punjabi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Punjabi
Context triple: [Hyderabad (Sindh), language, Punjabi]
  • A. Punjabi
    Punjabi refers to the ethnolinguistic group native to the Punjab region of South Asia, known for its distinct language, culture, and traditions shared across parts of India and Pakistan.
  • B. Punjabi language chosen
    Punjabi language is an Indo-Aryan language widely spoken in the Punjab region of India and Pakistan and among large diaspora communities worldwide.
  • C. Sindhi
    Sindhi is an Indo-Aryan language spoken primarily in Pakistan and India, known for its rich literary tradition and distinct script variants.
  • D. Dogri
    Dogri is an Indo-Aryan language spoken primarily in the Jammu region of India and surrounding areas, recognized as one of the official languages of India.
  • 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_69bd446b57bc8190a513d2e6c40314f3 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd854eb3248190b42a4b52f1c81bef completed March 20, 2026, 5:35 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf188d3a2c8190ad06d1b71ef73780 completed March 21, 2026, 10:15 p.m.
Created at: March 20, 2026, 1:54 p.m.