Triple
T2933508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sena |
E79208
|
entity |
| Predicate | closelyRelatedTo |
P37
|
FINISHED |
| Object | Nyanja |
E136466
|
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: Nyanja | Statement: [Sena, closelyRelatedTo, Nyanja]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nyanja Context triple: [Sena, closelyRelatedTo, Nyanja]
-
A.
Nyanja
chosen
Nyanja is a major Bantu language spoken primarily in Malawi, Zambia, Mozambique, and Zimbabwe, known for serving as a lingua franca in parts of southern Africa.
-
B.
Kigoma
Kigoma is a port city in western Tanzania located on the eastern shore of Lake Tanganyika and serving as a key regional transport and trade hub.
-
C.
Kalangala
Kalangala is a town on Uganda’s Ssese Islands in Lake Victoria, serving as the administrative and commercial center of Kalangala District.
-
D.
Kibondo
Kibondo is a town in western Tanzania that serves as an administrative and commercial center in the Kigoma Region.
-
E.
Kagera Region
Kagera Region is a northwestern region of Tanzania bordering Lake Victoria and several East African countries, known for its diverse ethnic groups, agriculture, and historical significance.
- 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_69ad8b0fbab081908f6a61567c045d8d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad983b65f881909b8b7d3dc5c224fd |
completed | March 8, 2026, 3:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b0867796808190a026c165e759f3ea |
completed | March 10, 2026, 9 p.m. |
Created at: March 8, 2026, 2:56 p.m.