Triple

T23476589
Position Surface form Disambiguated ID Type / Status
Subject Yao people E570279 entity
Predicate language P15 FINISHED
Object Kim Mun 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: Kim Mun language | Statement: [Yao people, language, Kim Mun language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kim Mun language
Context triple: [Yao people, language, Kim Mun language]
  • A. Kim Mun language chosen
    The Kim Mun language is a Hmong-Mien language spoken primarily by the Kim Mun (Yao) ethnic group in parts of China and Southeast Asia.
  • B. Kim language
    The Kim language is a Central Chadic (Afro-Asiatic) language spoken by the Kim people in parts of Chad.
  • C. Munji language
    The Munji language is an Eastern Iranian language spoken by the Munji people in Afghanistan’s remote Munjan Valley, closely related to the Yidgha language of Pakistan.
  • D. Baeggu language
    The Baeggu language is an Oceanic language spoken by the Baeggu people in the Solomon Islands, belonging to the Southeast Solomonic branch of the Austronesian language family.
  • E. Jangil language
    The Jangil language is an extinct and poorly documented Ongan language once spoken by the Jangil (Rutland Island) people of the Andaman Islands in India.
  • 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_69e245af8a88819084f2704f6d265a92 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1a74cf57081909d2b90a806d68c08 completed April 29, 2026, 6:38 a.m.
Created at: April 17, 2026, 6:01 p.m.