Triple

T502352
Position Surface form Disambiguated ID Type / Status
Subject Northern India E10427 entity
Predicate majorLanguage P207 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: [Northern India, majorLanguage, Dogri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dogri
Context triple: [Northern India, majorLanguage, 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. Saraiki
    Saraiki is an Indo-Aryan language spoken primarily in central and southern Pakistan, especially in the southern Punjab region.
  • C. Sindhi
    Sindhi is an Indo-Aryan language spoken primarily in Pakistan and India, known for its rich literary tradition and distinct script variants.
  • D. Sarnami Hindustani
    Sarnami Hindustani is a Hindi–Bhojpuri-based Indo-Aryan language developed among Indo-Caribbean communities, particularly in Suriname, from the speech of Indian indentured laborers.
  • E. Khari Boli
    Khari Boli is a major dialect of the Hindi-Urdu language continuum, historically associated with the Delhi region and serving as the primary basis for Standard Hindi.
  • 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_69a2e848adf881908e5e04f7af030093 completed Feb. 28, 2026, 1:06 p.m.
NER Named-entity recognition batch_69a2f1339748819089f89691a1698dd9 completed Feb. 28, 2026, 1:44 p.m.
NED1 Entity disambiguation (via context triple) batch_69a48a79ef808190a9dc34b58e16a160 completed March 1, 2026, 6:50 p.m.
Created at: Feb. 28, 2026, 1:12 p.m.