Triple
T23476091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitonga |
E570267
|
entity |
| Predicate | isRelatedTo |
P37
|
FINISHED |
| Object | Ronga 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: Ronga language | Statement: [Bitonga, isRelatedTo, Ronga language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ronga language Context triple: [Bitonga, isRelatedTo, Ronga language]
-
A.
Ronga language
chosen
The Ronga language is a Bantu language spoken primarily in southern Mozambique, closely related to Tsonga and used by the Ronga people in the Maputo region.
-
B.
Runga language
The Runga language is a Central Sudanic language spoken primarily by the Runga people in parts of Chad and the Central African Republic.
-
C.
Karanga language
The Karanga language is a member of the Maban branch of the Nilo-Saharan language family, spoken by communities in the central African region.
-
D.
Reang language
Reang language is a Tibeto-Burman tribal language spoken primarily by the Reang (Bru) community of Tripura and neighboring regions in Northeast India.
-
E.
Aringa language
The Aringa language is a Central Sudanic language spoken primarily by the Aringa people in northwestern Uganda.
- 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_69e245af8a88819084f2704f6d265a92 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a74cf57081909d2b90a806d68c08 |
completed | April 29, 2026, 6:38 a.m. |
Created at: April 17, 2026, 6:01 p.m.