Triple
T1838093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Somali |
E41110
|
entity |
| Predicate | nativeName |
P15
|
FINISHED |
| Object | Af-Soomaali |
E41110
|
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: Af-Soomaali | Statement: [Somali, nativeName, Af-Soomaali]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Af-Soomaali Context triple: [Somali, nativeName, Af-Soomaali]
-
A.
Somali
chosen
Somali is a Cushitic language spoken primarily in Somalia and neighboring regions of the Horn of Africa, serving as a major lingua franca and national language for the Somali people.
-
B.
Badaga language
Badaga language is a Southern Dravidian language spoken primarily by the Badaga community in the Nilgiri Hills of Tamil Nadu, India.
-
C.
Tamasheq
Tamasheq is a Berber language spoken by the Tuareg people of the central Sahara region.
-
D.
Oromo
Oromo is a Cushitic language widely spoken by the Oromo people, primarily in Ethiopia and parts of neighboring East African countries.
-
E.
Sudanese
Sudanese refers to people, culture, or things originating from the Northeast African country of Sudan.
- 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_69a88647f9388190909bc36e795bdaec |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb039cb588190b2626245a7f0bd67 |
completed | March 7, 2026, 4:57 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69adc9b93cd08190a467b56a0c0bd957 |
completed | March 8, 2026, 7:10 p.m. |
Created at: March 4, 2026, 7:33 p.m.