Triple

T22849942
Position Surface form Disambiguated ID Type / Status
Subject Prinmi language E566329 entity
Predicate closelyRelatedTo P37 FINISHED
Object Muya 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: Muya language | Statement: [Prinmi language, closelyRelatedTo, Muya language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Muya language
Context triple: [Prinmi language, closelyRelatedTo, Muya language]
  • A. Muya language chosen
    The Muya language is a lesser-known Sino-Tibetan language spoken by the Muya people in parts of Sichuan, China, noted for its complex phonology and endangered status.
  • B. Mumuye language
    The Mumuye language is a Niger-Congo language spoken primarily by the Mumuye people in northeastern Nigeria.
  • C. Namuyi language
    The Namuyi language is a lesser-known Sino-Tibetan language spoken by the Namuyi people in parts of Sichuan and Yunnan in southwestern China.
  • D. Muria language
    Muria language is a Central Dravidian language spoken primarily by the Muria Gond tribal communities in central India, especially in parts of Chhattisgarh and Maharashtra.
  • E. Puyuma language
    The Puyuma language is an endangered Austronesian language spoken by the Puyuma Indigenous people of southeastern Taiwan.
  • 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_69e2458750b481908a8e4cf4609cc6cf completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17eb74700819090d191b3a7a17034 completed April 29, 2026, 3:44 a.m.
Created at: April 17, 2026, 3:36 p.m.