Triple
T34058707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Programa Universidade para Todos |
E873433
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Brazilian public policy |
C61065
|
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 public policy Context triple: [Programa Universidade para Todos, instanceOf, Brazilian public policy]
-
A.
Brazilian economic development plan
A Brazilian economic development plan is a strategic framework of policies, investments, and reforms designed to promote sustainable growth, reduce inequality, and enhance the country’s long-term competitiveness.
-
B.
política pública urbana
Política pública urbana é o conjunto de ações, normas e instrumentos planejados e implementados pelo poder público para orientar o desenvolvimento das cidades, organizar o uso do território e promover bem-estar, equidade e sustentabilidade no espaço urbano.
-
C.
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.
-
D.
Brazilian law
Brazilian law is the legal system of Brazil, based on civil law traditions and the Federal Constitution of 1988, governing the rights, duties, and relationships of individuals, organizations, and the state.
-
E.
public policy agenda
A public policy agenda is a prioritized set of issues, goals, and proposed actions that guides government decision-making and resource allocation over a defined period.
- 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_69f349a4af208190afa14888f9c9fb9d |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:52 a.m.