Triple
T7458959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COSIPLAN |
E176194
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | UNASUR infrastructure council |
C8044
|
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: UNASUR infrastructure council Context triple: [COSIPLAN, instanceOf, UNASUR infrastructure council]
-
A.
sectoral council of UNASUR
chosen
The sectoral council of UNASUR is a specialized body that brings together member states’ ministers and experts in a specific policy area to coordinate regional strategies, harmonize initiatives, and promote integration within that sector across South America.
-
B.
UNASUR organ
A UNASUR organ is an institutional body within the Union of South American Nations responsible for carrying out specific functions such as decision-making, coordination, or implementation of the organization's policies and initiatives.
-
C.
MERCOSUR institution
A MERCOSUR institution is an organizational body within the Southern Common Market (MERCOSUR) framework responsible for formulating, coordinating, or implementing policies and decisions that govern regional economic, political, and social integration among member states.
-
D.
MERCOSUR organ
A MERCOSUR organ is an institutional body within the Southern Common Market (MERCOSUR) responsible for decision-making, coordination, implementation, or advisory functions related to the bloc’s regional integration policies and agreements.
-
E.
organ of the Andean Community
An organ of the Andean Community is an institutional body established by the Andean integration system to perform specific decision-making, advisory, executive, or administrative functions in support of the Community’s objectives and legal framework.
- 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_69c69f21632481908bf83f6c6da897e3 |
completed | March 27, 2026, 3:15 p.m. |
Created at: March 27, 2026, 3:36 p.m.