Triple

T21666913
Position Surface form Disambiguated ID Type / Status
Subject Kayanic E534745 entity
Predicate hasMember P10 FINISHED
Object Modang 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: Modang language | Statement: [Kayanic, hasMember, Modang language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Modang language
Context triple: [Kayanic, hasMember, Modang language]
  • A. Modang language chosen
    The Modang language is an Austronesian language spoken by the Modang people of Borneo, primarily in East Kalimantan, Indonesia.
  • B. 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.
  • C. 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.
  • D. Baangi language
    The Baangi language is a lesser-known Nupoid (Benue–Congo) language spoken by a small community in Nigeria.
  • E. Maonan language
    The Maonan language is a Kam–Sui language of the Tai–Kadai family spoken primarily by the Maonan ethnic group in southern China.
  • 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_69e0c46898008190aa618a4af55bd1ee completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef6c0c236881909ffaefea8601b1c2 completed April 27, 2026, 2 p.m.
Created at: April 16, 2026, 6:37 p.m.