Triple

T21718445
Position Surface form Disambiguated ID Type / Status
Subject Takr E536090 entity
Predicate usedForLanguage P907 FINISHED
Object Kangri NE NERFINISHED

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: Kangri | Statement: [Takr, usedForLanguage, Kangri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kangri
Context triple: [Takr, usedForLanguage, Kangri]
  • A. Kangri chosen
    Kangri is an Indo-Aryan language spoken primarily in the Kangra region of Himachal Pradesh in northern India.
  • B. Kangri Pahari
    Kangri Pahari is an Indo-Aryan language variety spoken primarily in the Kangra region of Himachal Pradesh in northern India.
  • C. Surkhuri
    Surkhuri is a traditional winter solstice festival of the Chuvash people, marked by rituals, feasting, and folk customs celebrating the turning of the year.
  • D. Kumaoni
    Kumaoni is an Indo-Aryan language spoken primarily in the Kumaon region of India’s Uttarakhand state, known for its rich oral traditions and distinct dialects.
  • E. Poonchi
    Poonchi is a regional Indo-Aryan language variety spoken in the Poonch area of the western Himalayas, closely related to other dialects of the greater Pahari–Punjabi linguistic zone.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c46c6dd88190a595375fa6ebd701 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69efd96cc58081908dda09819041b888 completed April 27, 2026, 9:47 p.m.
Created at: April 16, 2026, 6:47 p.m.