Triple

T5825682
Position Surface form Disambiguated ID Type / Status
Subject Mfecane E129216 entity
Predicate hasKeyGroup P46138 FINISHED
Object Kololo E250949 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: Kololo | Statement: [Mfecane, hasKeyGroup, Kololo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kololo
Context triple: [Mfecane, hasKeyGroup, Kololo]
  • A. Kololo chosen
    Kololo refers to the Sotho-speaking people whose 19th-century migration and conquest in south-central Africa significantly influenced the formation and language of the Lozi kingdom in present-day Zambia.
  • B. Chambeali
    Chambeali is an Indo-Aryan language spoken primarily in the Chamba region of Himachal Pradesh in northern India.
  • C. Oshikwambi
    Oshikwambi is a regional dialect of the Oshiwambo language spoken by the Kwambi people in northern Namibia.
  • D. Kandia
    Kandia is a remote valley and settlement area located within Pakistan’s Kohistan mountain ranges, known for its rugged terrain and isolated communities.
  • E. Kivili
    Kivili is a regional dialect of the Kikongo language spoken by communities in parts of Central Africa.
  • 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_69c00849d55481908b4f9f5543e0bf6d completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c0341a85988190be988f1c0722da66 completed March 22, 2026, 6:25 p.m.
NED1 Entity disambiguation (via context triple) batch_69c0985e3e748190abcc226abdcdb4b5 completed March 23, 2026, 1:33 a.m.
Created at: March 22, 2026, 3:53 p.m.