Triple
T23647358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maroua II |
E584073
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | local administrative subdivision |
C15097
|
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: local administrative subdivision Context triple: [Maroua II, instanceOf, local administrative subdivision]
-
A.
third-tier administrative subdivision
A third-tier administrative subdivision is a local governmental unit that operates below the second-tier division within a country's hierarchical administrative structure, typically managing community-level services and regulations.
-
B.
rural administrative district
A rural administrative district is a defined geographic area outside urban centers that is governed as a single unit for local administration, services, and regulation of predominantly agricultural or sparsely populated communities.
-
C.
local governmental entity
chosen
A local governmental entity is an administrative organization, such as a city, county, or district, that exercises governmental authority and provides public services within a specific geographic area below the level of the central or national government.
-
D.
subdivision of district
A subdivision of district is an administrative unit that forms a smaller, constituent part of a larger district within a governmental or organizational hierarchy.
-
E.
regulatory subdivision
A regulatory subdivision is a defined geographic or administrative area within a jurisdiction established for the purpose of applying, enforcing, or managing specific regulations, policies, or legal requirements.
- 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_69e248fefafc81909656921192f30e80 |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:48 p.m.