Triple
T6518296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States expressed concern and avoided labeling it a coup |
E148318
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | foreign policy stance |
C12226
|
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 stance Context triple: [United States expressed concern and avoided labeling it a coup, instanceOf, foreign policy stance]
-
A.
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.
-
B.
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.
-
C.
diplomatic policy
chosen
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.
diplomatic position
A diplomatic position is an official role within a government or international organization responsible for managing and representing a state's or entity's interests in foreign relations and negotiations.
-
E.
United States foreign policy doctrine
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.
- 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_69c687e68e748190baceb9298f32d3ed |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 1:44 p.m.