Triple
T24469909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CFSP |
E617070
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Common Foreign and Security Policy |
C24690
|
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: Common Foreign and Security Policy Context triple: [CFSP, instanceOf, Common Foreign and Security Policy]
-
A.
foreign and security policy body
A foreign and security policy body is an institutional entity responsible for formulating, coordinating, and overseeing a state’s external relations and national security strategies, including diplomacy, defense, and international cooperation.
-
B.
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.
-
C.
Common Foreign and Security Policy act
chosen
The Common Foreign and Security Policy act is a legislative or policy framework that governs a state's or union's collective approach to external relations, defense, and security cooperation with other countries and international organizations.
-
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.
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_69e2d7f197588190889a03e620558059 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:20 a.m.