Triple
T37962874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Territory of Guaporé |
E947052
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former federal territory of Brazil |
C66535
|
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: former federal territory of Brazil Context triple: [Federal Territory of Guaporé, instanceOf, former federal territory of Brazil]
-
A.
former Brazilian province
A former Brazilian province is a historical administrative division of Brazil that existed before the 1889 proclamation of the republic, after which these provinces were reorganized into modern states.
-
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.
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.
-
D.
former province of Portugal
A former province of Portugal is a historical administrative region that once served as a primary territorial division of the country but has since been reorganized or abolished in later administrative reforms.
-
E.
former territory of the United States
A former territory of the United States is a region that was once under U.S. territorial jurisdiction but later changed status, typically becoming a state, an independent nation, or part of another country.
- 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_69f76ef7062c819091bfacb7e83aa1e0 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.