Triple
T6177965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Region |
E137865
|
entity |
| Predicate | hasLanguage |
P15
|
FINISHED |
| Object | Gonja language |
E267649
|
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: Gonja language | Statement: [Northern Region, hasLanguage, Gonja language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gonja language Context triple: [Northern Region, hasLanguage, Gonja language]
-
A.
Gonja language
chosen
The Gonja language is a Gur language spoken primarily by the Gonja people in northern Ghana.
-
B.
Ghanongga language
The Ghanongga language is an Oceanic language spoken by indigenous communities on New Georgia Island in the Solomon Islands.
-
C.
Sanglechi language
The Sanglechi language is an Eastern Iranian language spoken by a small community in the Sanglech Valley region of Afghanistan and Tajikistan.
-
D.
Dagbani language
Dagbani is a major Gur language of northern Ghana, spoken primarily by the Dagomba people and used widely in education, media, and regional communication.
-
E.
Guna language
Guna language is an indigenous Chibchan language spoken by the Guna people of Panama and Colombia.
- 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_69c008a80f748190ba3d07ffc81acb29 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05dc9f3d88190ab46b3b246f5a8df |
completed | March 22, 2026, 9:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c141bb426881908d5a1451b3619f03 |
completed | March 23, 2026, 1:35 p.m. |
Created at: March 22, 2026, 4:18 p.m.