Triple

T21665205
Position Surface form Disambiguated ID Type / Status
Subject Echilómwe E534695 entity
Predicate hasAlternativeName P39 FINISHED
Object Lomwe 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: Lomwe | Statement: [Echilómwe, hasAlternativeName, Lomwe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lomwe
Context triple: [Echilómwe, hasAlternativeName, Lomwe]
  • A. Lomwe chosen
    Lomwe is a Bantu language spoken primarily in Mozambique and Malawi by the Lomwe people.
  • B. Luanshya
    Luanshya is a mining town in Zambia known for its copper production and role in the country’s Copperbelt region.
  • C. Vhavenda
    Vhavenda are a Bantu-speaking ethnic group primarily inhabiting the northern part of South Africa’s Limpopo Province, known for their rich cultural traditions, distinctive music and dance, and historical Venda kingdom.
  • D. Thabazimbi
    Thabazimbi is a small mining town in South Africa’s Limpopo province, known for its iron ore industry and proximity to the scenic Marakele National Park.
  • E. Makhuwa
    Makhuwa is a major Bantu language spoken primarily in northern Mozambique by the Makhuwa people.
  • 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_69e0c467e1f48190af2650b19175abc4 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef6c0b26c8819092c13e59dcc3c25c completed April 27, 2026, 2 p.m.
Created at: April 16, 2026, 6:36 p.m.