Triple
T18174647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andean Community member states |
E435124
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional economic bloc member grouping |
C31387
|
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: regional economic bloc member grouping Context triple: [Andean Community member states, instanceOf, regional economic bloc member grouping]
-
A.
regional cooperation bloc
A regional cooperation bloc is an alliance of neighboring countries that coordinate policies and collaborate on economic, political, or security issues to advance shared regional interests.
-
B.
regional trade union
A regional trade union is an organization that represents and advocates for the collective interests, rights, and working conditions of workers within a specific geographic region or group of neighboring countries.
-
C.
regional organisation
chosen
A regional organisation is an entity formed by multiple countries or territories within a specific geographic area to coordinate policies, promote cooperation, and address shared economic, political, social, or security issues.
-
D.
Economic alliance
An economic alliance is a formal or informal partnership between countries or regions designed to promote mutual economic benefits through cooperation in trade, investment, and financial policies.
-
E.
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.
- 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_69d8b90b7a188190b3fc7b8d4a6cd20a |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:30 a.m.