Triple
T8585638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Region, Uganda |
E203299
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | region of Uganda |
C24677
|
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: region of Uganda Context triple: [Central Region, Uganda, instanceOf, region of Uganda]
-
A.
district of Tanzania
A district of Tanzania is an administrative subdivision within a region, governed by local authorities responsible for implementing national policies and providing public services at the local level.
-
B.
country in East Africa
A country in East Africa is a sovereign nation located in the eastern region of the African continent, typically bordering the Indian Ocean or situated within the adjacent inland area.
-
C.
province of the Democratic Republic of the Congo
A province of the Democratic Republic of the Congo is a primary administrative division of the country, governed by provincial authorities and responsible for local administration, development, and implementation of national policies within its territory.
-
D.
region of Cameroon
A region of Cameroon is a top-level administrative division of the country, governed by a regional council and governor, encompassing multiple departments, cities, and communities with shared geographic, cultural, and economic characteristics.
-
E.
country in Central Africa
A country in Central Africa is a sovereign state located in the central region of the African continent, typically characterized by diverse ethnic groups, tropical or equatorial climates, and economies often based on natural resources and agriculture.
- 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_69ca8329bb7c8190a63c643730839103 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:22 p.m.