Triple
T4387387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andean Presidential Council |
E99277
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional integration body |
C11923
|
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 integration body Context triple: [Andean Presidential Council, instanceOf, regional integration body]
-
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 body of an international organization
chosen
A regional body of an international organization is a geographically focused subdivision that implements the organization’s policies, coordinates activities, and represents its interests within a specific region.
-
C.
intergovernmental legal body
An intergovernmental legal body is an organization formed by multiple governments to develop, interpret, or oversee the implementation of international legal norms, agreements, and dispute-resolution mechanisms.
-
D.
European intergovernmental organization
A European intergovernmental organization is a cooperative institution formed by European states through treaties to coordinate policies, manage shared interests, and address cross-border issues while preserving national sovereignty.
-
E.
intergovernmental organization
An intergovernmental organization is a formal entity created by sovereign states through treaties or agreements to cooperate on common interests, coordinate policies, and address international issues.
- 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_69b3454f739481909ff6c28331f0c0b9 |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:19 p.m.