Triple

T21053809
Position Surface form Disambiguated ID Type / Status
Subject Kami language E518655 entity
Predicate neighboringLanguage P16383 FINISHED
Object Zaramo language NE NERFINISHED

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: Zaramo language | Statement: [Kami language, neighboringLanguage, Zaramo language]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Zaramo language
Context triple: [Kami language, neighboringLanguage, Zaramo language]
  • A. Zaramo language chosen
    The Zaramo language is a Bantu language spoken primarily by the Zaramo people of eastern Tanzania, particularly around the coastal region near Dar es Salaam.
  • B. Giriama language
    The Giriama language is a Bantu language spoken primarily by the Giriama, one of the Mijikenda communities along Kenya’s coastal region.
  • C. Tembe language
    The Tembe language is an indigenous Tupi-Guarani language spoken by the Tembé people of northern Brazil.
  • D. Ngamo language
    The Ngamo language is a West Chadic language spoken primarily in northeastern Nigeria by the Ngamo people.
  • E. Sangirese language
    The Sangirese language is an Austronesian language spoken primarily by the Sangirese people of the Sangihe Islands in northern Indonesia.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b5053ac48190921529544959e906 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e6fd7e087c81908712ddc63e8b1e6c completed April 21, 2026, 4:30 a.m.
Created at: April 16, 2026, 2:36 p.m.