Triple
T5936703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yoshida Doctrine |
E132061
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Japanese foreign policy |
C3482
|
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: Japanese foreign policy Context triple: [Yoshida Doctrine, instanceOf, Japanese foreign policy]
-
A.
Japanese government doctrine
Japanese government doctrine refers to the evolving set of principles, legal interpretations, and policy norms that guide Japan’s constitutional governance, security policy, and administrative decision-making within the framework of its pacifist constitution and parliamentary democracy.
-
B.
Japanese diplomatic mission
A Japanese diplomatic mission is an official government delegation, such as an embassy or consulate, representing Japan abroad to manage political, economic, cultural, and consular relations with the host country or international organization.
-
C.
foreign policy journal
A foreign policy journal is a periodical publication that analyzes and critiques international relations, diplomatic strategies, and global political developments.
-
D.
foreign policy agenda
chosen
A foreign policy agenda is a strategic set of priorities, goals, and planned actions that guide a state's interactions and relationships with other countries and international actors.
-
E.
United States foreign policy
United States foreign policy is the strategic framework of decisions, actions, and principles through which the U.S. government manages its political, economic, military, and diplomatic relations with other countries and international organizations.
- 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_69c0085c55dc8190aa90e242c956e2fa |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 4:01 p.m.