Triple

T9951501
Position Surface form Disambiguated ID Type / Status
Subject Jammu Division E195340 entity
Predicate hasLanguage P15 FINISHED
Object Dogri E37893 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: Dogri | Statement: [Jammu Division, hasLanguage, Dogri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dogri
Context triple: [Jammu Division, hasLanguage, Dogri]
  • A. Dogri chosen
    Dogri is an Indo-Aryan language spoken primarily in the Jammu region of India and surrounding areas, recognized as one of the official languages of India.
  • B. Gojri
    Gojri is an Indo-Aryan language traditionally spoken by the Gujjar community across parts of northern India and Pakistan.
  • C. Kashmiri
    Kashmiri refers to the ethnic group native to the Kashmir Valley in the northern part of the Indian subcontinent, known for its distinct language, culture, and traditions.
  • D. Garhwali
    Garhwali is an Indo-Aryan language spoken primarily in the Garhwal region of the Indian state of Uttarakhand.
  • E. Pahari-Pothwari
    Pahari-Pothwari is an Indo-Aryan language variety spoken primarily in the Pothohar Plateau of northern Pakistan and adjoining regions, often considered transitional between Punjabi and Hindko.
  • 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_69ca82e96a108190932bd1fc4acd73a0 completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cdb6922f888190b5c4b58fbe21bea2 completed April 2, 2026, 12:21 a.m.
NED1 Entity disambiguation (via context triple) batch_69d23d5c6fdc81909b44d0b321201222 completed April 5, 2026, 10:45 a.m.
Created at: March 30, 2026, 8:46 p.m.