Triple
T29906080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porto Maravilha urban revitalization project |
E759538
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public–private partnership project |
C12274
|
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: public–private partnership project Context triple: [Porto Maravilha urban revitalization project, instanceOf, public–private partnership project]
-
A.
public–private partnership company
A public–private partnership company is an entity formed through collaboration between government and private sector organizations to finance, build, and operate projects or services traditionally provided by the public sector.
-
B.
public-sector collaboration
Public-sector collaboration is the coordinated effort among government agencies and public institutions, often with private and nonprofit partners, to jointly design, implement, and manage policies or services that address shared societal challenges.
-
C.
collaborative project
chosen
A collaborative project is a coordinated effort in which multiple individuals or groups work together, sharing responsibilities, resources, and expertise to achieve a common goal.
-
D.
intergovernmental partnership
An intergovernmental partnership is a collaborative arrangement in which two or more governments coordinate policies, resources, and actions to address shared issues or achieve common goals.
-
E.
innovation partnership
An innovation partnership is a collaborative relationship between organizations or individuals formed to co-create, develop, and implement new ideas, technologies, or solutions that deliver mutual value.
- 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_69f224600590819085e148a01c056ef6 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:08 p.m.