Triple

T11860494
Position Surface form Disambiguated ID Type / Status
Subject Mominabad E282144 entity
Predicate hasLanguage P15 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: [Mominabad, hasLanguage, Sindhi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sindhi
Context triple: [Mominabad, hasLanguage, 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. Kashmiri
    Kashmiri refers to the ethnic group native to the Kashmir Valley in the northern part of the Indian subcontinent, known for its distinct language, culture, and traditions.
  • D. Abbottabadi Hindko
    Abbottabadi Hindko is a regional variety of the Hindko language spoken primarily in and around the city of Abbottabad in northern Pakistan.
  • E. Saraiki
    Saraiki is an Indo-Aryan language spoken primarily in central and southern Pakistan, especially in the southern Punjab region.
  • 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_69d6ab287ba48190a5178779fd19b9b7 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8a69a099c8190a674db64c50eca5a completed April 10, 2026, 7:28 a.m.
NED1 Entity disambiguation (via context triple) batch_69f417a954e881909fdd9626d41229e2 completed May 1, 2026, 3:02 a.m.
Created at: April 8, 2026, 9:43 p.m.