Triple
T16033601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gamo-Gofa-Dawro |
E388910
|
entity |
| Predicate | hasPart |
P35
|
FINISHED |
| Object | Gofa language |
E511081
|
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: Gofa language | Statement: [Gamo-Gofa-Dawro, hasPart, Gofa language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gofa language Context triple: [Gamo-Gofa-Dawro, hasPart, Gofa language]
-
A.
Gofa language
chosen
The Gofa language is an Omotic language of southwestern Ethiopia spoken by the Gofa people and closely related to Wolaytta.
-
B.
Bafia language
The Bafia language is a Bantu language spoken primarily by the Bafia people in central Cameroon.
-
C.
Gokana language
Gokana language is a Niger-Congo language spoken by the Gokana people of Rivers State in Nigeria and is one of the principal Ogoni languages.
-
D.
Tofa language
Tofa is a critically endangered Turkic language traditionally spoken by the Tofa (Tofalars) people of south-central Siberia in Russia.
-
E.
Gupa-Abawa language
The Gupa-Abawa language is a Nupoid language spoken by the Gupa and Abawa peoples of central Nigeria.
- 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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1833a5aa88190a5cc3f82d55f5b62 |
completed | April 17, 2026, 12:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffcf373f548190abfc93aa238b97fd |
completed | May 10, 2026, 12:20 a.m. |
Created at: April 10, 2026, 4:56 a.m.