Triple

T11114861
Position Surface form Disambiguated ID Type / Status
Subject Mandura Gumuz E262859 entity
Predicate name P16 FINISHED
Object Mandura Gumuz E262859 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: Mandura Gumuz | Statement: [Mandura Gumuz, name, Mandura Gumuz]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mandura Gumuz
Context triple: [Mandura Gumuz, name, Mandura Gumuz]
  • A. Mandura Gumuz chosen
    Mandura Gumuz is a Gumuz language spoken by the Gumuz people of western Ethiopia.
  • B. Mundemba
    Mundemba is a town in southwestern Cameroon known as a gateway to the biodiverse Korup National Park.
  • C. Ngola
    Ngola is an alternative name for the Angolar people, a community of African descent primarily associated with São Tomé and Príncipe.
  • D. Matsigenka
    The Matsigenka are an Indigenous people of the Peruvian Amazon known for their forest-based subsistence lifestyle, distinct language, and rich shamanic and cosmological traditions.
  • E. Lefua
    Lefua is a genus of small freshwater loaches native to East Asia, known for inhabiting cool, clear streams and belonging to the stone loach family.
  • 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_69d6aa9b46cc8190b19f9f0cc45bf322 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d79aa7254c8190abce35696ad2be03 completed April 9, 2026, 12:25 p.m.
NED1 Entity disambiguation (via context triple) batch_69e42d7da99881908d38ea66c37dfb92 completed April 19, 2026, 1:18 a.m.
Created at: April 8, 2026, 9:27 p.m.