Triple

T2875673
Position Surface form Disambiguated ID Type / Status
Subject Beihai E56871 entity
Predicate languageUsed P238 FINISHED
Object Zhuang language E126954 NE FINISHED

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: Zhuang language | Statement: [Beihai, languageUsed, Zhuang language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Zhuang language
Context triple: [Beihai, languageUsed, Zhuang language]
  • A. Zhuang language chosen
    The Zhuang language is a Tai-Kadai language spoken primarily by the Zhuang ethnic group in Guangxi and surrounding regions of southern China.
  • B. Siwu language
    The Siwu language is a Niger-Congo language spoken primarily in the Volta Region of Ghana by the Mawu people.
  • C. Miao languages
    The Miao languages are a group of Hmong-Mien (Miao-Yao) languages spoken primarily by the Miao people across southern China and parts of Southeast Asia.
  • D. Kaili language
    The Kaili language is an Austronesian language spoken primarily in Central Sulawesi, Indonesia, known for its multiple dialects and role as a regional lingua franca.
  • E. Jingpo language
    The Jingpo language is a Tibeto-Burman language spoken primarily by the Jingpo (Kachin) people in northern Myanmar and adjacent regions of China and India.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69ab4a4ced288190ab6d3e062d10f7f6 completed March 6, 2026, 9:42 p.m.
NER Named-entity recognition batch_69abe004a64481908f1897d9054a7368 completed March 7, 2026, 8:21 a.m.
NED1 Entity disambiguation (via context triple) batch_69b01dbb28588190ba2daae192744908 completed March 10, 2026, 1:33 p.m.
Created at: March 6, 2026, 10:03 p.m.