Triple
T9890713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASEAN centrality |
E181442
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | principle of Indo-Pacific regionalism |
C20026
|
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: principle of Indo-Pacific regionalism Context triple: [ASEAN centrality, instanceOf, principle of Indo-Pacific regionalism]
-
A.
regional institutional system
A regional institutional system is a coordinated network of organizations, rules, and practices within a specific geographic area that collectively shape governance, economic activity, and social outcomes.
-
B.
ASEAN policy document
chosen
An ASEAN policy document is an official written instrument produced by ASEAN bodies that articulates agreed regional principles, commitments, and courses of action on specific political, economic, social, or security issues among member states.
-
C.
SAARC policy instrument
A SAARC policy instrument is a formal mechanism—such as agreements, action plans, frameworks, or guidelines—adopted by the South Asian Association for Regional Cooperation to coordinate and implement regional policies among member states.
-
D.
Micronesian regional organization
A Micronesian regional organization is an entity that facilitates political, economic, social, and environmental cooperation among the island nations and territories of Micronesia.
-
E.
interregional relations
Interregional relations are the political, economic, social, and cultural interactions and institutionalized connections that occur between distinct geographic regions within or across states.
- 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_69ca8283a6708190801af7a25a7ebb9f |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 8:39 p.m.