Triple
T23055682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plano de Metas |
E574149
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Brazilian economic development plan |
C47186
|
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: Brazilian economic development plan Context triple: [Plano de Metas, instanceOf, Brazilian economic development plan]
-
A.
Portuguese colonial project
The Portuguese colonial project was a long-term, state-backed enterprise of maritime exploration, conquest, trade, religious conversion, and settlement that established a dispersed but influential global empire from the 15th to the 20th century.
-
B.
Mexican political plan
A Mexican political plan is a formal, often revolutionary, document that outlines a political movement’s principles, goals, and strategies for restructuring or challenging the existing government in Mexico.
-
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.
Brazilian federal complementary law
A Brazilian federal complementary law is a special type of statute, approved by an absolute majority in the National Congress, that supplements and details constitutional provisions on matters expressly reserved by the Federal Constitution.
-
E.
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.
- 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_69e245ba7ae48190be606dbc54120e39 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:55 p.m.