Triple

T21917134
Position Surface form Disambiguated ID Type / Status
Subject Bamileke languages E541208 entity
Predicate hasMember P10 FINISHED
Object Ghomáláʼ language 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: Ghomáláʼ language | Statement: [Bamileke languages, hasMember, Ghomáláʼ language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ghomáláʼ language
Context triple: [Bamileke languages, hasMember, Ghomáláʼ language]
  • A. Ghomáláʼ language chosen
    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.
  • B. Ghomara language
    The Ghomara language is a lesser-known Berber language spoken by the Ghomara people in northern Morocco.
  • C. Halchidhoma language
    The Halchidhoma language is an extinct Yuman language once spoken by the Halchidhoma people along the lower Colorado River in the southwestern United States.
  • D. Nomlaki language
    The Nomlaki language is an endangered Native American language traditionally spoken by the Nomlaki people of northern California.
  • E. Glaro-Twabo language
    The Glaro-Twabo language is a lesser-known Kru language spoken by communities in West Africa, particularly in Liberia and neighboring regions.
  • 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_69e0c47c4b9c8190a5586a75f5f36453 completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f1233858308190a877d8015db4d380 completed April 28, 2026, 9:14 p.m.
Created at: April 16, 2026, 7:43 p.m.