Triple
T6647696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inter-American system |
E150743
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | network of regional organizations |
C10807
|
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: network of regional organizations Context triple: [Inter-American system, instanceOf, network of regional organizations]
-
A.
regional collaborative network
chosen
A regional collaborative network is a structured alliance of organizations, institutions, and stakeholders within a specific geographic area that coordinate resources, knowledge, and activities to address shared goals and regional challenges.
-
B.
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.
-
C.
regional organisation of councils
A regional organisation of councils is a collaborative body formed by multiple local government councils within a geographic region to coordinate planning, share resources, and advocate on common regional issues.
-
D.
regional partnership
A regional partnership is a collaborative alliance among organizations, governments, or stakeholders within a specific geographic area to coordinate resources, strategies, and initiatives toward shared economic, social, or environmental goals.
-
E.
transnational organization
A transnational organization is an entity that operates across multiple countries, coordinating activities, resources, and decision-making beyond the authority or boundaries of any single nation-state.
- 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_69c687f1a3048190828b7342f7125d5c |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 2 p.m.