Triple
T6136721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agreement on the Common Effective Preferential Tariff (CEPT) Scheme for the ASEAN Free Trade Area |
E136851
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ASEAN treaty |
C566
|
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 treaty Context triple: [Agreement on the Common Effective Preferential Tariff (CEPT) Scheme for the ASEAN Free Trade Area, instanceOf, ASEAN treaty]
-
A.
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.
-
B.
treaty
chosen
A treaty is a formal, legally binding agreement between two or more sovereign states or international entities that defines their mutual rights, obligations, and commitments.
-
C.
treaty-based alliance
A treaty-based alliance is a formal agreement between two or more sovereign entities that legally binds them to cooperate on specified political, military, economic, or other mutual interests under defined terms and obligations.
-
D.
treaty annex
A treaty annex is a supplementary document attached to a main treaty that provides detailed provisions, technical specifications, or additional terms that form an integral part of the overall agreement.
-
E.
annex to international agreement
An annex to an international agreement is a supplementary document formally attached to the main treaty that provides detailed provisions, technical specifications, or additional obligations that are integral to and legally binding under the agreement.
- 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_69c008a179388190a3b5a081bbf46d55 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:15 p.m.