Triple
T9890712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASEAN centrality |
E181442
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | norm in international relations |
C26609
|
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: norm in international relations Context triple: [ASEAN centrality, instanceOf, norm in international relations]
-
A.
international order
International order is the overarching system of rules, institutions, norms, and power relationships that structure how states and other global actors interact, cooperate, and compete.
-
B.
international relations
International relations is the study and practice of how states and other global actors interact, cooperate, and conflict within the international system.
-
C.
subject of international law
A subject of international law is an entity recognized by the international legal system as having rights, duties, and the capacity to act on the international plane, such as states, international organizations, and in some cases individuals.
-
D.
system of international law
A system of international law is a structured set of principles, rules, and institutions that govern the rights, duties, and interactions of states and other international actors in their relations with one another.
-
E.
international normative instrument
An international normative instrument is a formal document, such as a treaty, convention, declaration, or guideline, adopted by states or international organizations to establish shared standards, principles, or rules of conduct in the international arena.
- 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.