Triple

T7355305
Position Surface form Disambiguated ID Type / Status
Subject Buru E169608 entity
Predicate languageSpoken P151 FINISHED
Object Buru language E652717 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: Buru language | Statement: [Buru, languageSpoken, Buru language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Buru language
Context triple: [Buru, languageSpoken, Buru language]
  • A. Buru languages chosen
    Buru languages are a small group of closely related Austronesian languages spoken primarily on Buru Island in Indonesia’s Maluku region.
  • B. 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.
  • C. Embaloh language
    The Embaloh language is an Austronesian language spoken by the Embaloh people of West Kalimantan in Borneo, Indonesia.
  • D. Bima language
    Bima language is an Austronesian language spoken primarily on Sumbawa Island in Indonesia, known for its distinct grammar and vocabulary within the region.
  • E. 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.
  • 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_69c68a59f2288190877ca15c19b1e822 completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f139505c8190a7158cf59a6e089e completed March 27, 2026, 9:06 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7faa25960819084ecb6dbf9369ba5 completed March 28, 2026, 3:58 p.m.
Created at: March 27, 2026, 3:05 p.m.