Triple

T21870378
Position Surface form Disambiguated ID Type / Status
Subject Bunun people E539984 entity
Predicate language P15 FINISHED
Object Bunun 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: Bunun language | Statement: [Bunun people, language, Bunun language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bunun language
Context triple: [Bunun people, language, Bunun language]
  • A. Bunun language chosen
    The Bunun language is an Austronesian language spoken by the Bunun indigenous people of central and southern Taiwan, known for its complex verb morphology and rich oral traditions.
  • B. Bungin language
    The Bungin language is an Austronesian language spoken by the Bungin people of South Sulawesi, Indonesia, and is part of the Massenrempulu subgroup.
  • C. Bunak language
    The Bunak language is a Papuan language spoken primarily in the central region of Timor, straddling the border between Indonesia and Timor-Leste.
  • D. Bo language
    Bo language is an extinct Great Andamanese language once spoken by the Bo people of the Andaman Islands in India.
  • E. Buin language
    The Buin language is an Austronesian language spoken by the Buin people of southern Bougainville in Papua New Guinea.
  • 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_69e0c478f59081909d54302b57fc1ce3 completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f0f33509d08190b33775abb84d5255 completed April 28, 2026, 5:49 p.m.
Created at: April 16, 2026, 6:57 p.m.