Triple

T15944841
Position Surface form Disambiguated ID Type / Status
Subject Gamo E386657 entity
Predicate hasAlternativeName P39 FINISHED
Object Gamo language E511080 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: Gamo language | Statement: [Gamo, hasAlternativeName, Gamo language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gamo language
Context triple: [Gamo, hasAlternativeName, Gamo language]
  • A. Gamo language chosen
    The Gamo language is an Omotic language of southwestern Ethiopia spoken by the Gamo people and closely related to neighboring Wolaytta.
  • B. Ghomara language
    The Ghomara language is a lesser-known Berber language spoken by the Ghomara people in northern Morocco.
  • C. Pokomo language
    The Pokomo language is a Bantu language spoken primarily by the Pokomo people along Kenya’s Tana River.
  • D. Patamona language
    The Patamona language is an indigenous Cariban language spoken by the Patamona people of the Guiana Highlands in Guyana and northern Brazil.
  • E. Ghomáláʼ language
    Ghomáláʼ is a major Bantu language of the Grassfields region in western Cameroon, spoken primarily by the Bamiléké people and known for its rich tonal system.
  • 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_69d86da882448190a82ea962fe343b79 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e156d016588190ae368197dfa7d43a completed April 16, 2026, 9:38 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffb5beabbc8190977f14c1b3ccdf29 completed May 9, 2026, 10:31 p.m.
Created at: April 10, 2026, 4:53 a.m.