Triple

T13623007
Position Surface form Disambiguated ID Type / Status
Subject Amarkot E325503 entity
Predicate languageUsed P238 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: [Amarkot, languageUsed, Sindhi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sindhi
Context triple: [Amarkot, languageUsed, 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_69d8076aae28819092cf636190ee5529 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbbe9b0b648190afee93121483f45f completed April 12, 2026, 3:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69f77fa4c5fc8190bd791f181fce2aa1 completed May 3, 2026, 5:02 p.m.
Created at: April 9, 2026, 9:50 p.m.