Triple

T8278182
Position Surface form Disambiguated ID Type / Status
Subject Jola language E193598 entity
Predicate closelyRelatedTo P37 FINISHED
Object Balanta language E605131 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: Balanta language | Statement: [Jola language, closelyRelatedTo, Balanta language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Balanta language
Context triple: [Jola language, closelyRelatedTo, Balanta language]
  • A. Balanta language chosen
    The Balanta language is a Niger-Congo language spoken primarily by the Balanta people of Guinea-Bissau and neighboring West African countries.
  • B. Balantak language
    The Balantak language is an Austronesian language spoken by the Balantak people of eastern Central Sulawesi, Indonesia.
  • C. Kalanguya language
    The Kalanguya language is an Austronesian language spoken by the Kalanguya people in the northern Luzon highlands of the Philippines.
  • D. Banda-Linda language
    The Banda-Linda language is a Banda language spoken by the Banda-Linda people of the Central African Republic.
  • E. Baliledu language
    The Baliledu language is an Austronesian language of the Bima–Sumba subgroup spoken by a local community in eastern Indonesia.
  • 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_69ca82e217a48190880695635c44b2ed completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb79ebb6b88190bc777b8bd72fcdbc completed March 31, 2026, 7:38 a.m.
NED1 Entity disambiguation (via context triple) batch_69cd6863c22c8190b888a23bb9005712 completed April 1, 2026, 6:48 p.m.
Created at: March 30, 2026, 5:51 p.m.