Triple
T36118248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Minas Gerais |
E1044669
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subregion of Minas Gerais |
C46812
|
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: subregion of Minas Gerais Context triple: [Southern Minas Gerais, instanceOf, subregion of Minas Gerais]
-
A.
microregion of Brazil
A microregion of Brazil is a geographic and statistical subdivision within a mesoregion, defined by the Brazilian Institute of Geography and Statistics (IBGE) to group neighboring municipalities with similar economic and social characteristics for planning and analysis purposes.
-
B.
region of Santa Catarina
A region of Santa Catarina is a geographically defined subdivision of the Brazilian state of Santa Catarina characterized by shared economic, cultural, environmental, and administrative attributes.
-
C.
mesoregion of Brazil
chosen
A mesoregion of Brazil is an intermediate geographic and statistical subdivision within a state, grouping together neighboring municipalities that share similar economic, social, and natural characteristics.
-
D.
macroregion of Brazil
A macroregion of Brazil is a large, officially defined territorial division that groups multiple states based on geographic, economic, social, and cultural similarities for planning and statistical purposes.
-
E.
district of São Paulo
A district of São Paulo is an administrative subdivision of the municipality that organizes local governance, public services, and community identity within a defined urban territory.
- 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_69f76e344a4c8190af3858c6d78ba88f |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.