Triple

T9051979
Position Surface form Disambiguated ID Type / Status
Subject Mon Khmer E216904 entity
Predicate includesLanguage P2177 FINISHED
Object Bru language E775521 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: Bru language | Statement: [Mon Khmer, includesLanguage, Bru language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bru language
Context triple: [Mon Khmer, includesLanguage, 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. Batui language
    The Batui language is an Austronesian language spoken in Central Sulawesi, Indonesia, and is part of the Saluan–Banggai subgroup.
  • 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_69ca83d362e88190ae44b4e4dc194209 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cc7a700de48190aa9f61d850e01cbd completed April 1, 2026, 1:52 a.m.
NED1 Entity disambiguation (via context triple) batch_69cffdbd54848190ba79d873321f4fc9 completed April 3, 2026, 5:49 p.m.
Created at: March 30, 2026, 7:10 p.m.