Triple

T6511087
Position Surface form Disambiguated ID Type / Status
Subject Namibia and Botswana E150133 entity
Predicate shareLanguageFamilyPresence P64840 FINISHED
Object Bantu languages LITERAL 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: Bantu languages | Statement: [Namibia and Botswana, shareLanguageFamilyPresence, Bantu languages]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: shareLanguageFamilyPresence
Context triple: [Namibia and Botswana, shareLanguageFamilyPresence, Bantu languages]
  • A. isInLanguageFamily
    Indicates that a language belongs to, or is classified within, a particular language family based on shared linguistic ancestry or characteristics.
  • B. inLanguageFamily
    Indicates that two languages belong to the same linguistic family or classification.
  • C. usesLanguageFamily chosen
    Indicates that an entity communicates or operates using a language that belongs to a specified language family.
  • D. languageFamilyAssociated
    Indicates that there is an association or connection between a language and a particular language family.
  • E. languageFamilyStatus
    Indicates the classification or recognition status of a language within a particular language family (e.g., primary, branch, extinct, or disputed).
  • F. None of above.

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_69c687ef291081909d437f035eef1cda completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c69f3ad7d081909162f1a625fc52b1 completed March 27, 2026, 3:16 p.m.
PD Predicate disambiguation batch_69c68ab98c78819081743e614df04e1d completed March 27, 2026, 1:48 p.m.
Created at: March 27, 2026, 1:43 p.m.