Triple

T7344509
Position Surface form Disambiguated ID Type / Status
Subject Garhwali E169341 entity
Predicate hasDialect P4251 FINISHED
Object Pauri Garhwali E169341 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: Pauri Garhwali | Statement: [Garhwali, hasDialect, Pauri Garhwali]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pauri Garhwali
Context triple: [Garhwali, hasDialect, Pauri Garhwali]
  • A. Garhwali chosen
    Garhwali is an Indo-Aryan language spoken primarily in the Garhwal region of the Indian state of Uttarakhand.
  • B. Maithili
    Maithili is an Indo-Aryan language spoken primarily in the eastern Indian state of Bihar and neighboring regions, with a rich literary tradition and official recognition in India.
  • C. Nagpuri
    Nagpuri is an Indo-Aryan language spoken primarily in parts of eastern India, especially in and around the present-day state of Jharkhand.
  • D. Bhojpuri
    Bhojpuri is an Indo-Aryan language spoken primarily in eastern Uttar Pradesh, western Bihar, and parts of Nepal, with a rich folk culture and a large diaspora community.
  • E. Bagheli
    Bagheli is an Indo-Aryan language spoken primarily in the Bagelkhand region of central India, closely related to Hindi and used by millions as a regional vernacular.
  • 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_69c68a57710481909f0c1f3c6ebdb6f2 completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f0ed78908190a169f094cb3f62f0 completed March 27, 2026, 9:04 p.m.
NED1 Entity disambiguation (via context triple) batch_69c802b24194819096b796de15d66ed2 completed March 28, 2026, 4:32 p.m.
Created at: March 27, 2026, 3:05 p.m.