Triple

T11510221
Position Surface form Disambiguated ID Type / Status
Subject Hindkowans E272889 entity
Predicate associatedLanguageName P13426 FINISHED
Object Hindko language 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 language | Statement: [Hindkowans, associatedLanguageName, Hindko language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hindko language
Context triple: [Hindkowans, associatedLanguageName, Hindko language]
  • 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. Swati language
    Swati language is a Bantu language of the Nguni group spoken primarily in Eswatini and parts of South Africa.
  • D. Bihari languages
    Bihari languages are a group of closely related Indo-Aryan languages spoken primarily in the Bihar region of eastern India and neighboring areas.
  • E. Gojri
    Gojri is an Indo-Aryan language traditionally spoken by the Gujjar community across parts of northern India and Pakistan.
  • 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_69d6aae2c3748190bed2ea50dfb160dc completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d86db65eb081908613a1002c6a4fb4 completed April 10, 2026, 3:25 a.m.
NED1 Entity disambiguation (via context triple) batch_69ee86853e088190a9c1378aad45fa18 completed April 26, 2026, 9:41 p.m.
Created at: April 8, 2026, 9:36 p.m.