Triple
T29668657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arsi dialect |
E750604
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | variety of Oromo language |
C56056
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: variety of Oromo language Context triple: [Arsi dialect, instanceOf, variety of Oromo language]
-
A.
variety of Somali language
A variety of Somali language is a distinct regional or social form of Somali characterized by unique phonological, lexical, and grammatical features within the broader Somali linguistic continuum.
-
B.
Gurage language variety
A Gurage language variety is a specific form of speech within the Gurage branch of South Ethiosemitic languages, distinguished by its unique phonological, lexical, and grammatical features used by particular Gurage communities in Ethiopia.
-
C.
variety of the Berom language
A variety of the Berom language is a distinct regional or social form of Berom characterized by systematic differences in pronunciation, vocabulary, or grammar while remaining mutually intelligible with other forms.
-
D.
variety of Ewe language
A variety of Ewe language is a distinct regional or social form of the Ewe language characterized by unique phonological, lexical, or grammatical features while remaining mutually intelligible with other Ewe forms.
-
E.
variety of Ossetian language
A variety of Ossetian language is a distinct regional or social form of Ossetian characterized by specific phonological, lexical, and grammatical features within the broader Ossetian linguistic continuum.
- F. None of above. chosen
Provenance (1 batch)
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_69f0d62418a08190a401b127adf9f8a6 |
completed | April 28, 2026, 3:45 p.m. |
Created at: April 28, 2026, 7:02 p.m.