Triple
T9936783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North American Group |
E193978
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional division of the Trilateral Commission |
C2248
|
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 division of the Trilateral Commission Context triple: [North American Group, instanceOf, regional division of the Trilateral Commission]
-
A.
regional division
chosen
A regional division is an organizational unit that segments a larger geographic area into distinct regions for administrative, operational, or strategic management purposes.
-
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.
division of the United Nations
A division of the United Nations is an organizational unit within the UN system responsible for carrying out specialized functions, programs, or administrative tasks in support of the organization's overarching goals and mandates.
-
D.
Trilateral Commission report
A Trilateral Commission report is a formal analytical document produced by the Trilateral Commission that examines global political, economic, or security issues and offers policy recommendations for cooperation among North America, Europe, and Asia-Pacific.
-
E.
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.
- 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_69ca82e409348190a393777356b80a2a |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 8:44 p.m.