Triple
T36711711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2015 Joint Strategic Vision for the Asia–Pacific and Indian Ocean Region |
E906810
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | foreign policy document |
C39383
|
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: foreign policy document Context triple: [2015 Joint Strategic Vision for the Asia–Pacific and Indian Ocean Region, instanceOf, foreign policy document]
-
A.
foreign policy statement
chosen
A foreign policy statement is an official declaration by a government outlining its principles, goals, and intended actions in relations with other states and international actors.
-
B.
international diplomatic document
An international diplomatic document is a formal written instrument exchanged between states or international organizations to record, communicate, or formalize agreements, positions, or understandings in the conduct of foreign relations.
-
C.
foreign policy domain
The foreign policy domain encompasses the strategies, decisions, and actions through which a state manages its relationships and interactions with other international actors to pursue its national interests.
-
D.
foreign policy proposal
A foreign policy proposal is a structured plan outlining a government's intended strategies, actions, and positions in its relations with other nations and international organizations.
-
E.
foreign policy practice
Foreign policy practice is the systematic application of strategies, decisions, and actions by a state or international actor to manage its relationships and pursue its interests in the global arena.
- 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_69f76e73ad108190a5241585f2303e9a |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:12 p.m.