Triple

T11303161
Position Surface form Disambiguated ID Type / Status
Subject Lobi language E267645 entity
Predicate hasAlternativeName P39 FINISHED
Object Lobiri language E267645 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: Lobiri language | Statement: [Lobi language, hasAlternativeName, Lobiri language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lobiri language
Context triple: [Lobi language, hasAlternativeName, Lobiri language]
  • A. Lobi language chosen
    The Lobi language is a Gur language spoken primarily by the Lobi people in parts of Burkina Faso, Côte d’Ivoire, and Ghana.
  • B. Logba language
    The Logba language is a Niger-Congo language spoken by the Logba people of southeastern Ghana.
  • C. Loniu language
    The Loniu language is an Oceanic language spoken on Loniu Island in Manus Province, Papua New Guinea.
  • D. Lozi language
    The Lozi language is a Bantu language spoken primarily in western Zambia and surrounding regions, serving as the main language of the Lozi people and a lingua franca in parts of south-central Africa.
  • E. Luri language
    Luri language is a Southwestern Iranian language spoken primarily by the Lur people in western and southwestern Iran.
  • 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_69e525b4bdb88190b22d64eb65e97d9d completed April 19, 2026, 6:57 p.m.
Created at: April 8, 2026, 9:32 p.m.