Triple
T23239320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASEAN Economic Community Blueprint 2015 |
E581392
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional economic integration blueprint |
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 economic integration blueprint Context triple: [ASEAN Economic Community Blueprint 2015, instanceOf, regional economic integration blueprint]
-
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 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.
-
C.
regional economic zone
A regional economic zone is a geographically defined area within or across countries where economic policies, regulations, and incentives are coordinated to promote trade, investment, and development.
-
D.
ASEAN economic integration measure
An ASEAN economic integration measure is a policy, agreement, or instrument adopted by ASEAN member states to reduce barriers, harmonize regulations, and promote the free flow of goods, services, investment, capital, and skilled labor within the region.
-
E.
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.
- 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_69e2460556f88190be1744a84a84173f |
completed | April 17, 2026, 2:39 p.m. |
Created at: April 17, 2026, 4:10 p.m.