Triple
T5689481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal District (Brazil) |
E125393
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | first-level administrative division of Brazil |
C6418
|
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 Brazil Context triple: [Federal District (Brazil), instanceOf, first-level administrative division of Brazil]
-
A.
federative unit of Brazil
chosen
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.
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.
-
C.
first-level administrative division of the Philippines
A first-level administrative division of the Philippines is a primary local government unit, such as a province, highly urbanized city, or independent component city, directly under the national government and above municipalities and barangays in the administrative hierarchy.
-
D.
federal unit
A federal unit is a constituent political entity, such as a state or province, within a federal system that shares sovereignty with a central government while retaining certain autonomous powers.
-
E.
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.
- 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_69c0082bb19c8190823a4facd3cba79b |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:44 p.m.