Triple

T20837834
Position Surface form Disambiguated ID Type / Status
Subject Bru people E513008 entity
Predicate language P15 FINISHED
Object Bru 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: Bru language | Statement: [Bru people, language, Bru language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bru language
Context triple: [Bru people, language, Bru language]
  • A. Bru language chosen
    Bru language is a Mon–Khmer language spoken by the Bru people across parts of Laos, Vietnam, and Thailand.
  • B. Bo language
    Bo language is an extinct Great Andamanese language once spoken by the Bo people of the Andaman Islands in India.
  • C. Berom language
    The Berom language is a Plateau language spoken primarily by the Berom people in Nigeria’s Middle Belt region, especially around Jos in Plateau State.
  • D. Bel languages
    Bel languages are a small group of closely related Austronesian languages spoken primarily along the north coast of Papua New Guinea.
  • E. Buyi language
    The Buyi language is a Tai–Kadai language spoken primarily by the Buyi ethnic group in Guizhou and neighboring regions of 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_69e0b4cf62a88190bbf92351e9e57259 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c3280a1881909a86d1fe498aee50 completed April 21, 2026, 12:22 a.m.
Created at: April 16, 2026, 12:42 p.m.