Triple
T19718620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISM |
E473545
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | MERCOSUR body |
C16499
|
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: MERCOSUR body Context triple: [ISM, instanceOf, MERCOSUR body]
-
A.
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.
-
B.
MERCOSUR institution
chosen
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.
-
C.
Pacific Alliance body
A Pacific Alliance body is an organizational entity established by the Pacific Alliance to coordinate, implement, or oversee specific areas of regional integration and cooperation among its member states.
-
D.
principal organ of the Union of South American Nations
The principal organ of the Union of South American Nations is its highest decision-making body responsible for setting the organization’s overall political direction, policies, and priorities among member states.
-
E.
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.
- 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:46 p.m.