Triple
T37787108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO–Warsaw Pact conventional balance |
E941982
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | international security concept |
C8275
|
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: international security concept Context triple: [NATO–Warsaw Pact conventional balance, instanceOf, international security concept]
-
A.
international relations
International relations is the study and practice of how states and other global actors interact, cooperate, and conflict within the international system.
-
B.
homeland security concept
A homeland security concept is a strategic framework that integrates policies, resources, and coordinated actions to prevent, protect against, respond to, and recover from threats and hazards to a nation’s people, infrastructure, and institutions.
-
C.
international relations infrastructure
International relations infrastructure encompasses the institutions, communication systems, legal frameworks, and logistical networks that enable states and international actors to coordinate, negotiate, and implement cross-border policies and agreements.
-
D.
international order
chosen
International order is the overarching system of rules, institutions, norms, and power relationships that structure how states and other global actors interact, cooperate, and compete.
-
E.
national security policy
National security policy is a government’s overarching framework of principles, strategies, and actions designed to protect a nation’s sovereignty, citizens, and critical interests from internal and external threats.
- 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_69f76ee5cb0c81909a363d1c929156c0 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.