Triple

T11302733
Position Surface form Disambiguated ID Type / Status
Subject Southern Gur languages E267635 entity
Predicate hasLanguage P15 FINISHED
Object Sisaala language E267644 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: Sisaala language | Statement: [Southern Gur languages, hasLanguage, Sisaala language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sisaala language
Context triple: [Southern Gur languages, hasLanguage, Sisaala language]
  • A. Sisaala language chosen
    The Sisaala language is a Gur language spoken primarily by the Sisaala people in northern Ghana and parts of Burkina Faso.
  • B. Sanglechi language
    The Sanglechi language is an Eastern Iranian language spoken by a small community in the Sanglech Valley region of Afghanistan and Tajikistan.
  • C. Saisiyat language
    The Saisiyat language is an indigenous Austronesian language spoken by the Saisiyat people of northwestern Taiwan.
  • D. Saluan language
    The Saluan language is an Austronesian language spoken by the Saluan people of central and eastern Sulawesi, Indonesia.
  • E. Asilulu language
    The Asilulu language is an Austronesian language spoken by the Asilulu people on Ambon Island in Indonesia’s Maluku province.
  • 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_69d6aac993a08190a6f36445ebaf9a43 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e9a5c3788190ba54eda514b97903 completed April 9, 2026, 6:02 p.m.
NED1 Entity disambiguation (via context triple) batch_69e50a57366081908a05fc52c5d4074c completed April 19, 2026, 5:01 p.m.
Created at: April 8, 2026, 9:32 p.m.