Triple
T23701065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASEAN consensus |
E585596
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ASEAN norm |
C19880
|
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: ASEAN norm Context triple: [ASEAN consensus, instanceOf, ASEAN norm]
-
A.
ASEAN legal instrument
An ASEAN legal instrument is a formal, collectively agreed document adopted by ASEAN member states that establishes binding or non-binding rules, commitments, or cooperative frameworks within the Association of Southeast Asian Nations.
-
B.
ASEAN policy document
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.
ASEAN document
chosen
An ASEAN document is an official written record, agreement, declaration, or communication produced or endorsed by the Association of Southeast Asian Nations to guide regional cooperation, policy, and governance among its member states.
-
D.
ASEAN-led mechanism
An ASEAN-led mechanism is a regional cooperative framework or process initiated, guided, and coordinated by the Association of Southeast Asian Nations to address political, economic, security, or socio-cultural issues in the Asia-Pacific region.
-
E.
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.
- 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_69e24904bd508190abfcb74855de2918 |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:53 p.m.