Triple

T23505814
Position Surface form Disambiguated ID Type / Status
Subject Kiranti E572278 entity
Predicate hasLanguage P15 FINISHED
Object Chamling NE NERFINISHED

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: Chamling | Statement: [Kiranti, hasLanguage, Chamling]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Chamling
Context triple: [Kiranti, hasLanguage, Chamling]
  • A. Chamling chosen
    Chamling is a Kiranti language of the Sino-Tibetan family spoken primarily by the Chamling people in eastern Nepal and neighboring regions.
  • B. Khaling Tsangla
    Khaling Tsangla is a regional dialect of the Tsangla language spoken by the Khaling community in parts of the eastern Himalayas.
  • C. Jampal
    Jampal is the Tibetan name for Manjushri, the bodhisattva in Mahayana Buddhism associated with transcendent wisdom and insight.
  • D. Gurung
    Gurung is a Sino-Tibetan language spoken primarily by the Gurung ethnic community from the Himalayan regions of Nepal and its diaspora, including Nepali Americans.
  • E. Kham Magar
    Kham Magar are a subgroup of the Magar people of Nepal, distinguished by their own Kham language and distinct cultural traditions in the mid-western Himalayan region.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e245b5e4208190bac8a6509867e394 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1a8ff97c88190a67f787e1674619e completed April 29, 2026, 6:45 a.m.
Created at: April 17, 2026, 6:07 p.m.