Triple
T21941033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ceilândia |
E541819
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative region of the Federal District of Brazil |
C45554
|
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 region of the Federal District of Brazil Context triple: [Ceilândia, instanceOf, administrative region of the Federal District of Brazil]
-
A.
administrative zone of Rio de Janeiro
An administrative zone of Rio de Janeiro is a territorial subdivision of the city used by the municipal government to organize and manage public services, planning, and administration across different urban regions.
-
B.
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.
-
C.
administrative district of São Paulo
An administrative district of São Paulo is a defined territorial subdivision of the municipality used for local governance, planning, and public service management.
-
D.
municipality of Brazil
A municipality of Brazil is the smallest autonomous administrative division in the country, governed by a mayor and municipal council, responsible for local public services, regulations, and development within its defined territory.
-
E.
state of Brazil
A state of Brazil is a primary administrative division of the country, possessing its own government, constitution, and defined territory within the Brazilian federation.
- 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_69e0c47e2e5c81909a7f74ce3de50911 |
completed | April 16, 2026, 11:14 a.m. |
Created at: April 16, 2026, 7:55 p.m.