Triple
T9890711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASEAN centrality |
E181442
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional governance principle |
C26608
|
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 governance principle Context triple: [ASEAN centrality, instanceOf, regional governance principle]
-
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.
regional division
A regional division is an organizational unit that segments a larger geographic area into distinct regions for administrative, operational, or strategic management purposes.
-
C.
regional administrative branch
A regional administrative branch is a localized division of a larger organization or government responsible for managing operations, implementing policies, and coordinating services within a specific geographic area.
-
D.
regional strategy
A regional strategy is a coordinated plan that aligns resources, initiatives, and policies to achieve specific objectives within a defined geographic area, considering its unique economic, cultural, and competitive context.
-
E.
Commonwealth governance guidelines
Commonwealth governance guidelines are a set of principles and best practices that direct how member states of the Commonwealth should structure, operate, and oversee their public institutions to ensure accountability, transparency, and the rule of law.
- F. None of above. chosen
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.