Triple

T7792435
Position Surface form Disambiguated ID Type / Status
Subject Banda people E180212 entity
Predicate language P15 FINISHED
Object Banda-Yangere E672480 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: Banda-Yangere | Statement: [Banda people, language, Banda-Yangere]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Banda-Yangere
Context triple: [Banda people, language, Banda-Yangere]
  • A. Banda-Yangere chosen
    Banda-Yangere is a dialect of the Central Banda language spoken by Banda communities in parts of Central Africa.
  • B. Ngbandi
    Ngbandi is a Central African language spoken primarily in the Democratic Republic of the Congo and the Central African Republic, known for its role as a regional lingua franca and its inclusion in the Ubangian language family.
  • C. Yassa
    Yassa was the codified legal and administrative code traditionally attributed to Genghis Khan that governed the Mongol Empire and its successor states.
  • D. Mbanderu
    Mbanderu is a subgroup of the Herero people with its own distinct dialect and cultural traditions, primarily found in Namibia and Botswana.
  • E. Yandabo
    Yandabo is a village in central Myanmar historically notable as the site where the Treaty of Yandabo ended the First Anglo-Burmese War in 1826.
  • 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_69ca827d22208190b4dc5aa680edcf5d completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cae938714c8190b89917e6ded004da completed March 30, 2026, 9:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69cb13cdb4288190ae3cfe1ee4e3e496 completed March 31, 2026, 12:22 a.m.
Created at: March 30, 2026, 4:30 p.m.