Triple

T3999096
Position Surface form Disambiguated ID Type / Status
Subject Northwestern Indo-Aryan languages E87168 entity
Predicate includesLanguage P2177 FINISHED
Object Hindko E198840 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: Hindko | Statement: [Northwestern Indo-Aryan languages, includesLanguage, Hindko]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hindko
Context triple: [Northwestern Indo-Aryan languages, includesLanguage, Hindko]
  • A. Hindko chosen
    Hindko is a group of Indo-Aryan dialects spoken primarily in northern Pakistan, especially in parts of Khyber Pakhtunkhwa and Azad Kashmir.
  • B. Sant Bhasha
    Sant Bhasha is a historical North Indian devotional literary language used in Sikh and related spiritual poetry, written in the Gurmukhi script.
  • C. Kurukh
    Kurukh is an indigenous Dravidian language spoken primarily by the Oraon tribal communities in eastern and central India.
  • D. Bagheli
    Bagheli is an Indo-Aryan language spoken primarily in the Bagelkhand region of central India, closely related to Hindi and used by millions as a regional vernacular.
  • E. Mirpuri
    Mirpuri is a major dialect of the Lahnda (Western Punjabi) language, primarily spoken in the Mirpur region of Azad Kashmir and among its diaspora communities.
  • 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_69aed94118148190975e6aa4e554cde9 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefa4065ac8190a898a1025365b8e9 completed March 9, 2026, 4:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69b54c57f60c819080e237b4b056d73b completed March 14, 2026, 11:54 a.m.
Created at: March 9, 2026, 3:34 p.m.