Triple
T7820902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stimson Doctrine regarding Manchuria |
E181124
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States diplomatic policy |
C417
|
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: United States diplomatic policy Context triple: [Stimson Doctrine regarding Manchuria, instanceOf, United States diplomatic policy]
-
A.
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.
-
B.
United States foreign policy doctrine
chosen
A United States foreign policy doctrine is a guiding framework of principles and strategic priorities that shapes how the U.S. engages with other nations and responds to international challenges.
-
C.
diplomatic policy
Diplomatic policy is a strategic framework guiding a state’s interactions and negotiations with other international actors to advance its political, economic, and security interests while managing conflicts and alliances.
-
D.
foreign policy agenda
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 federal policy
United States federal policy is the body of laws, regulations, and official actions enacted or implemented by the federal government to address national issues and guide public and private behavior across the country.
- 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_69ca828153f48190bdb27ac46f8e0745 |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 4:41 p.m.