Triple

T23506321
Position Surface form Disambiguated ID Type / Status
Subject Bodish languages E572290 entity
Predicate hasMember P10 FINISHED
Object Jirel 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: Jirel language | Statement: [Bodish languages, hasMember, Jirel language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jirel language
Context triple: [Bodish languages, hasMember, Jirel language]
  • A. Jirel language chosen
    The Jirel language is a Kiranti language of the Sino-Tibetan family spoken by the Jirel ethnic community in eastern Nepal.
  • B. Itsari language
    The Itsari language is a Northeast Caucasian (Dargin) variety spoken in Dagestan, Russia, closely related to the Kubachi language and used by a small local community.
  • C. Kaera language
    The Kaera language is a Papuan language spoken by a small community on Pantar Island in eastern Indonesia.
  • D. Saraveca language
    The Saraveca language is an extinct Arawakan language once spoken in Bolivia, known from very limited historical documentation.
  • E. Keiga language
    The Keiga language is a Kadu (Kadugli) language spoken by the Keiga people in the Nuba Mountains region of Sudan.
  • 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_69f1a9009ca081908c4cffb8c32293ec completed April 29, 2026, 6:45 a.m.
Created at: April 17, 2026, 6:07 p.m.