Triple

T14870351
Position Surface form Disambiguated ID Type / Status
Subject tso E349726 entity
Predicate represents P129 FINISHED
Object Tsonga language E135269 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: Tsonga language | Statement: [tso, represents, Tsonga language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tsonga language
Context triple: [tso, represents, Tsonga language]
  • A. Tsonga language chosen
    The Tsonga language is a Bantu language spoken primarily in southern Africa, especially in Mozambique, South Africa, Eswatini, and Zimbabwe.
  • B. Sanglechi language
    The Sanglechi language is an Eastern Iranian language spoken by a small community in the Sanglech Valley region of Afghanistan and Tajikistan.
  • C. Tembe language
    The Tembe language is an indigenous Tupi-Guarani language spoken by the Tembé people of northern Brazil.
  • D. Tontemboan language
    The Tontemboan language is an Austronesian language spoken by the Tontemboan people of North Sulawesi, Indonesia, and is one of the traditional Minahasan languages of the region.
  • E. Kalanga language
    The Kalanga language is a Bantu language spoken primarily by the Kalanga people in parts of Botswana and southwestern Zimbabwe.
  • 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_69d822ee4f408190b6ac3b2fa434f0df completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69ded57967748190a7c05ebb74aacb7c completed April 15, 2026, 12:02 a.m.
NED1 Entity disambiguation (via context triple) batch_69fe651067cc8190b9c218ef1f802762 completed May 8, 2026, 10:34 p.m.
Created at: April 10, 2026, 1:55 a.m.