Triple
T32526876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asia Pacific Group of the Trilateral Commission |
E831338
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional group of international policy discussion forum |
C562
|
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 group of international policy discussion forum Context triple: [Asia Pacific Group of the Trilateral Commission, instanceOf, regional group of international policy discussion forum]
-
A.
regional forum
chosen
A regional forum is a structured platform where stakeholders from a specific geographic area gather to discuss, coordinate, and address shared issues, policies, and development priorities.
-
B.
regional representative group
A regional representative group is an organized body of individuals chosen or appointed to advocate for and make decisions on behalf of stakeholders within a specific geographic area.
-
C.
international political forum
An international political forum is a structured platform where representatives from multiple countries convene to discuss, negotiate, and coordinate on global political, economic, and security issues.
-
D.
regional organisation
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.
-
E.
United Nations Regional Group
A United Nations Regional Group is a coalition of member states organized by geographic region to coordinate positions, facilitate negotiations, and allocate seats in UN bodies and committees.
- 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_69f34923e1548190be0524205d8cdf8f |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1:01 a.m.