Triple
T6842145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States (for Lon Nol government) |
E157798
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | foreign policy role |
C21333
|
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 role Context triple: [United States (for Lon Nol government), instanceOf, foreign policy role]
-
A.
foreign affairs ministerial role
A foreign affairs ministerial role is a high-level government position responsible for managing a nation's international relations, diplomacy, and foreign policy.
-
B.
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.
-
C.
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.
-
D.
international economic policy role
An international economic policy role involves analyzing global economic trends, negotiating and designing cross-border economic agreements, and advising governments or organizations on strategies that promote sustainable growth, trade, and financial stability.
-
E.
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.
- 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_69c6882ed4c081909dc465a7cf8838be |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:19 p.m.