Triple

T7344517
Position Surface form Disambiguated ID Type / Status
Subject Garhwali E169341 entity
Predicate hasAlternativeName P39 FINISHED
Object Gadhwali 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: Gadhwali | Statement: [Garhwali, hasAlternativeName, Gadhwali]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gadhwali
Context triple: [Garhwali, hasAlternativeName, Gadhwali]
  • A. Nagara Bhumija
    Nagara Bhumija is a distinctive sub-style of North Indian Hindu temple architecture characterized by a tall, curvilinear main tower surrounded by miniature spires arranged in a regular, grid-like pattern.
  • B. Garhwali chosen
    Garhwali is an Indo-Aryan language spoken primarily in the Garhwal region of the Indian state of Uttarakhand.
  • C. Madhesi
    Madhesi are an ethnolinguistic group from the southern plains of Nepal, culturally and linguistically close to communities across the border in northern India.
  • D. Bhutia
    Bhutia is a Sino-Tibetan language spoken primarily by the Bhutia community in the Himalayan regions of India, especially in Sikkim and parts of West Bengal.
  • E. Lepcha
    Lepcha is a Tibeto-Burman language spoken by the indigenous Lepcha people of the eastern Himalayas, particularly in and around Sikkim.
  • 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_69c7fa8de0888190b62101471048b8e1 completed March 28, 2026, 3:58 p.m.
Created at: March 27, 2026, 3:05 p.m.