Triple

T13460710
Position Surface form Disambiguated ID Type / Status
Subject Hindko people E311356 entity
Predicate language P15 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: [Hindko people, language, Hindko language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hindko language
Context triple: [Hindko people, language, 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. Haryanvi language
    Haryanvi language is an Indo-Aryan language spoken primarily in the Indian state of Haryana and surrounding regions, closely related to Hindi and often considered one of its dialects.
  • D. Swati language
    Swati language is a Bantu language of the Nguni group spoken primarily in Eswatini and parts of South Africa.
  • E. 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.
  • 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_69d806a938b8819097ec43a2229fc7f9 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69dbaf0c177081909178dec61b09c278 completed April 12, 2026, 2:41 p.m.
NED1 Entity disambiguation (via context triple) batch_69f7462522c88190a6a6e2e2292e2414 completed May 3, 2026, 12:57 p.m.
Created at: April 9, 2026, 9:41 p.m.