Triple

T14096686
Position Surface form Disambiguated ID Type / Status
Subject MSA languages E339269 entity
Predicate hasMember P10 FINISHED
Object Jibbali language E1079435 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: Jibbali language | Statement: [MSA languages, hasMember, Jibbali language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jibbali language
Context triple: [MSA languages, hasMember, Jibbali language]
  • A. Jibbali language chosen
    The Jibbali language, also known as Shehri, is a Modern South Arabian Semitic language spoken primarily by communities in southern Oman.
  • B. Dibo language
    The Dibo language is a Nupoid language spoken by the Dibo people of central Nigeria.
  • C. Teke-Ibali language
    The Teke-Ibali language is a Bantu language spoken by the Teke people in Central Africa, forming one of the distinct varieties within the broader Teke linguistic group.
  • D. Babanki language
    The Babanki language is a Grassfields Bantu language spoken by the Babanki people in Cameroon.
  • E. Saliba language
    The Saliba language is an Oceanic language spoken in Papua New Guinea, particularly in the Milne Bay Province, and is known for its role in local maritime and village communication.
  • 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_69d81c69b5c8819094aa1abf18302908 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de5fb926288190a7f0f50d1d585d76 completed April 14, 2026, 3:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69fcdf02638881908eff75453b6a2aab completed May 7, 2026, 6:50 p.m.
Created at: April 9, 2026, 10:22 p.m.