Triple
T26470413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portfolio of Priority Integration Projects |
E665883
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional integration instrument |
C44068
|
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 instrument Context triple: [Portfolio of Priority Integration Projects, instanceOf, regional integration instrument]
-
A.
regional economic integration protocol
A regional economic integration protocol is a formal agreement among neighboring or closely linked countries that coordinates trade, investment, and regulatory policies to reduce barriers and promote a more unified regional market.
-
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
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.
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.
-
E.
regional economic cooperation framework
chosen
A regional economic cooperation framework is an organized arrangement among neighboring countries to coordinate policies, reduce trade and investment barriers, and promote shared economic development and integration.
- 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_69ee883f80dc819090e311b022b78e02 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 27, 2026, 12:19 a.m.