Triple
T2718835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Capital Territory, Nigeria |
E60031
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | first-level administrative division of Nigeria |
C8821
|
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: first-level administrative division of Nigeria Context triple: [Federal Capital Territory, Nigeria, instanceOf, first-level administrative division of Nigeria]
-
A.
federative unit of Brazil
A federative unit of Brazil is a primary political and administrative division of the country—such as a state or the Federal District—with its own government, constitution, and limited autonomy under the Brazilian federal system.
-
B.
subdivision of Iraq
A subdivision of Iraq is an administrative region within the country, such as a governorate, district, or subdistrict, established for local governance and organizational purposes.
-
C.
federal capital territory
chosen
A federal capital territory is a distinct administrative region that serves as the seat of a nation's federal government and is typically governed directly by the national authority rather than by a state or provincial government.
-
D.
regional division
A regional division is an organizational unit that segments a larger geographic area into distinct regions for administrative, operational, or strategic management purposes.
-
E.
administrative territorial entity
An administrative territorial entity is a geographically defined area governed by an authority that exercises administrative, political, or legal control within its boundaries.
- 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_69ab4b746d248190958e052045c09255 |
completed | March 6, 2026, 9:47 p.m. |
Created at: March 6, 2026, 9:55 p.m.