Triple

T3337465
Position Surface form Disambiguated ID Type / Status
Subject Tsonga E70172 entity
Predicate hasDialect P4251 FINISHED
Object Ronga E154633 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: Ronga | Statement: [Tsonga, hasDialect, Ronga]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ronga
Context triple: [Tsonga, hasDialect, Ronga]
  • A. Ronga chosen
    Ronga is a Bantu language spoken primarily in southern Mozambique, known for contributing vocabulary and structural features to African varieties of Portuguese.
  • B. Tongaat
    Tongaat is a town in KwaZulu-Natal, South Africa, known for its significant Indian community and sugar industry.
  • C. Orongo
    Orongo is a ceremonial stone village and archaeological site on Easter Island, best known for its role in the Birdman cult and its dramatic clifftop setting overlooking the ocean.
  • D. Vangunu
    Vangunu is an Oceanic language of the Meso-Melanesian group spoken on Vangunu Island in the Solomon Islands.
  • E. Karanga
    Karanga is a major dialect of the Shona language spoken primarily in southern Zimbabwe, known for its distinct phonological and lexical features.
  • 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_69ad85a24f208190bcf83131bfed3521 completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb1bc31b4819085f01e0b5a7cbc5d completed March 8, 2026, 5:28 p.m.
NED1 Entity disambiguation (via context triple) batch_69b325191a38819095cdccca8f013774 completed March 12, 2026, 8:42 p.m.
Created at: March 8, 2026, 3:12 p.m.