Triple

T8265862
Position Surface form Disambiguated ID Type / Status
Subject ڈوگری E193299 entity
Predicate writingSystemOf P454 FINISHED
Object Dogri language 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 language | Statement: [ڈوگری, writingSystemOf, Dogri language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dogri language
Context triple: [ڈوگری, writingSystemOf, Dogri language]
  • 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 language
    Kashmiri language is an Indo-Aryan language spoken primarily in the Kashmir Valley, written in multiple scripts including a Perso-Arabic–based Nastaʿlīq script.
  • D. 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.
  • E. Punjabi language
    Punjabi language is an Indo-Aryan language widely spoken in the Punjab region of India and Pakistan and among large diaspora communities worldwide.
  • 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_69ca82e081d48190986beaa51f498ab9 completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb794c54448190a685b8d0070980d7 completed March 31, 2026, 7:35 a.m.
NED1 Entity disambiguation (via context triple) batch_69cd6827e44c81909be6e426ab9226c7 completed April 1, 2026, 6:47 p.m.
Created at: March 30, 2026, 5:50 p.m.