Triple

T15648348
Position Surface form Disambiguated ID Type / Status
Subject Kutchi E376238 entity
Predicate hasDialect P4251 FINISHED
Object Tharadari Kutchi E376238 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: Tharadari Kutchi | Statement: [Kutchi, hasDialect, Tharadari Kutchi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tharadari Kutchi
Context triple: [Kutchi, hasDialect, Tharadari Kutchi]
  • A. Thari Sindhi
    Thari Sindhi is a regional variety of the Sindhi language spoken primarily in the Thar Desert region spanning parts of Pakistan and India.
  • B. Kutchi chosen
    Kutchi is an Indo-Aryan language spoken primarily by the Kutchi people of the Kutch region in the Indian state of Gujarat and in diaspora communities abroad.
  • C. Tharkha
    Tharkha is a traditional musical form or instrument associated with the cultural heritage and folk music of the Bodo people of Northeast India.
  • D. Shekhani
    Shekhani is a dialect of the Kati language spoken by communities in parts of Afghanistan and Pakistan.
  • E. Dakhni
    Dakhni is a historical Indo-Aryan language variety that developed in the Deccan region of India, blending early Urdu/Hindavi with local languages and Persian-Arabic influences.
  • 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_69d85cd1564c8190991adda63bfab4b0 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04ed7212c8190be6ff76afa25f7ca completed April 16, 2026, 2:52 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff67936e388190913c9060194e5b53 completed May 9, 2026, 4:57 p.m.
Created at: April 10, 2026, 4:15 a.m.