Triple
T17357433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States (during Soviet–Afghan War) |
E421975
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state actor in an international conflict |
C5645
|
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: state actor in an international conflict Context triple: [United States (during Soviet–Afghan War), instanceOf, state actor in an international conflict]
-
A.
co-belligerent state
chosen
A co-belligerent state is a country that fights alongside another state against a common enemy in an armed conflict without necessarily being formally allied or bound by a mutual defense treaty.
-
B.
intra-state rivalry
Intra-state rivalry is a sustained, competitive relationship between distinct political, social, or armed actors operating within the same state who contest authority, resources, or legitimacy.
-
C.
side in civil conflict
A side in civil conflict is a distinct organized group or faction within a single country that participates as a primary party to internal armed hostilities, pursuing specific political, territorial, or ideological objectives.
-
D.
geopolitical conflict
A geopolitical conflict is a sustained struggle between nations or political entities driven by competing interests over territory, resources, ideology, or influence on the global stage.
-
E.
covert military conflict
A covert military conflict is a hidden or plausibly deniable struggle between states or organized groups that uses clandestine operations, proxies, and intelligence activities instead of overt, declared warfare.
- 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:44 a.m.