Triple

T5619814
Position Surface form Disambiguated ID Type / Status
Subject Rangat Tehsil E147571 entity
Predicate hasOfficialLanguage P236 FINISHED
Object Sindhi E12831 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: Sindhi | Statement: [Rangat Tehsil, hasOfficialLanguage, Sindhi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sindhi
Context triple: [Rangat Tehsil, hasOfficialLanguage, Sindhi]
  • A. Sindhi chosen
    Sindhi is an Indo-Aryan language spoken primarily in Pakistan and India, known for its rich literary tradition and distinct script variants.
  • B. 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.
  • C. Saraiki
    Saraiki is an Indo-Aryan language spoken primarily in central and southern Pakistan, especially in the southern Punjab region.
  • 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. Balochi
    Balochi is an Iranian language spoken primarily by the Baloch people across Pakistan, Iran, and Afghanistan, with several dialects and a rich oral literary tradition.
  • 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_69c00905d4588190bd967842bbcf2219 completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c022108db8819098739510366adee1 completed March 22, 2026, 5:08 p.m.
NED1 Entity disambiguation (via context triple) batch_69c05a0ed3748190875aacdf5e9ee211 completed March 22, 2026, 9:07 p.m.
Created at: March 22, 2026, 3:40 p.m.