Triple

T23505293
Position Surface form Disambiguated ID Type / Status
Subject Athpare language E572263 entity
Predicate isRelatedTo P37 FINISHED
Object Belhare language 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: Belhare language | Statement: [Athpare language, isRelatedTo, Belhare language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Belhare language
Context triple: [Athpare language, isRelatedTo, Belhare language]
  • A. Belhare language chosen
    The Belhare language is a Kiranti language of the Sino-Tibetan family spoken by the Belhare community in eastern Nepal.
  • B. Tharawal language
    Tharawal language is an Australian Aboriginal language traditionally spoken by the Tharawal people of coastal New South Wales, south of Sydney.
  • C. Halchidhoma language
    The Halchidhoma language is an extinct Yuman language once spoken by the Halchidhoma people along the lower Colorado River in the southwestern United States.
  • D. Kharia language
    Kharia language is a Munda language spoken primarily by the Kharia people in eastern India, especially in the states of Jharkhand, Odisha, and Chhattisgarh.
  • E. Bagvalal language
    The Bagvalal language is a Northeast Caucasian language spoken by the Bagvalal people in the Republic of Dagestan, Russia.
  • 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.