Triple
T23360735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boyo Division |
E593174
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative division of Cameroon |
C46498
|
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: administrative division of Cameroon Context triple: [Boyo Division, instanceOf, administrative division of Cameroon]
-
A.
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.
-
B.
department of Cameroon
chosen
A department of Cameroon is an administrative subdivision of the country, below the regional level, responsible for local governance, coordination of public services, and implementation of national policies within its territory.
-
C.
commune of Cameroon
A commune of Cameroon is the smallest administrative unit in the country, typically encompassing a town or group of villages, governed by a local council and mayor responsible for local development and public services.
-
D.
people of Cameroon
People of Cameroon are a diverse population composed of numerous ethnic, linguistic, and cultural groups, known for their rich traditions, vibrant arts, and dynamic blend of African and global influences.
-
E.
subnational division of Namibia
A subnational division of Namibia is an administrative region within the country, such as a region, constituency, or local authority area, established for governance, political representation, and public administration.
- F. None of above.
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_69e25d24d2a4819092e6ede74c2a918d |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:30 p.m.