Triple
T23053785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roadmap for an ASEAN Community 2009–2015 |
E574098
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional integration roadmap |
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 roadmap Context triple: [Roadmap for an ASEAN Community 2009–2015, instanceOf, regional integration roadmap]
-
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 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.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69e245ba7ae48190be606dbc54120e39 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:54 p.m.