Triple
T9671707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Lakes Bantu languages |
E234044
|
entity |
| Predicate | hasMember |
P10
|
FINISHED |
| Object | Runyoro |
E695723
|
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: Runyoro | Statement: [Great Lakes Bantu languages, hasMember, Runyoro]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Runyoro Context triple: [Great Lakes Bantu languages, hasMember, Runyoro]
-
A.
Runyoro
chosen
Runyoro is a Bantu language spoken primarily by the Banyoro people in western Uganda.
-
B.
Kwanyama
Kwanyama is a major standardized dialect of the Ovambo language spoken primarily in northern Namibia and southern Angola.
-
C.
Kiswah
Kiswah is the ornate black cloth embroidered with Quranic verses that traditionally drapes and adorns the Kaaba in Mecca.
-
D.
Lango
The Lango are a Nilotic ethnic group primarily inhabiting northern Uganda, known for their distinct language and cultural traditions.
-
E.
Nyaturu language
The Nyaturu language is a Bantu language spoken primarily by the Nyaturu people in central Tanzania.
- 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_69ca848f55e48190b3f67252571c3d45 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c6949108190b699442e5c2aacf9 |
completed | April 1, 2026, 10:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d18a28d1c481908737992466d35fdd |
completed | April 4, 2026, 10:01 p.m. |
Created at: March 30, 2026, 8:15 p.m.