Triple

T17297497
Position Surface form Disambiguated ID Type / Status
Subject Karibib E419948 entity
Predicate languageUsed P238 FINISHED
Object Afrikaans E5797 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: Afrikaans | Statement: [Karibib, languageUsed, Afrikaans]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Afrikaans
Context triple: [Karibib, languageUsed, Afrikaans]
  • A. Afrikaans chosen
    Afrikaans is a West Germanic language spoken mainly in South Africa and Namibia, originating from 17th-century Dutch and influenced by various African and Asian languages.
  • B. Siswati
    Siswati is a Bantu language of the Nguni group spoken primarily in Eswatini and South Africa, where it holds official status.
  • C. Afrikaansche Galey
    Afrikaansche Galey was a Dutch exploration ship notably associated with the early 18th-century Pacific voyages of navigator Jacob Roggeveen.
  • D. Xhosa
    Xhosa is a Bantu language of South Africa, known for its distinctive click consonants and as one of the country’s major official languages.
  • E. Tshivenda
    Tshivenda is a Bantu language spoken primarily by the Venda people in northern South Africa and neighboring regions.
  • 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_69d886db32608190a61e18862c5a8af6 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e438f82788819088ea796850552297 completed April 19, 2026, 2:07 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0180d881ec81908e794143d355effe completed May 11, 2026, 7:10 a.m.
Created at: April 10, 2026, 5:41 a.m.