Triple

T13863758
Position Surface form Disambiguated ID Type / Status
Subject Springbok E333266 entity
Predicate hasLanguage P15 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: [Springbok, hasLanguage, Afrikaans]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Afrikaans
Context triple: [Springbok, hasLanguage, 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. Afrikaansche Galey
    Afrikaansche Galey was a Dutch exploration ship notably associated with the early 18th-century Pacific voyages of navigator Jacob Roggeveen.
  • C. 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.
  • D. Tshivenda
    Tshivenda is a Bantu language spoken primarily by the Venda people in northern South Africa and neighboring regions.
  • E. Zulu
    Zulu is a Bantu language of the Nguni group spoken primarily in South Africa and widely influential in the country’s culture and other local languages.
  • 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_69d81c5ced9c8190b0e9bcc6effe5959 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de05c30d9c81908217d41a3b4aaf85 completed April 14, 2026, 9:15 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7c10113288190b799126d934df92a completed May 3, 2026, 9:41 p.m.
Created at: April 9, 2026, 10:14 p.m.