Triple
T4882028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet–Turkish conflicts (interwar period) |
E109349
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical conflict |
C543
|
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: historical conflict Context triple: [Soviet–Turkish conflicts (interwar period), instanceOf, historical conflict]
-
A.
geopolitical conflict
chosen
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.
-
B.
civil conflict
Civil conflict is a sustained, organized struggle within a country between the state and one or more internal groups, or among such groups themselves, involving political, social, or economic grievances and often resulting in violence.
-
C.
series of conflicts
A series of conflicts is a sequence of interconnected disputes, struggles, or confrontations that unfold over time, often escalating or evolving as parties respond to previous clashes.
-
D.
military confrontation
A military confrontation is an armed clash between organized state or non-state forces, involving the use or threat of force to achieve political, territorial, or strategic objectives.
-
E.
19th-century conflict
A 19th-century conflict is a large-scale military or political struggle occurring between 1800 and 1899, typically involving nation-states or empires and shaped by industrialization, nationalism, and shifting imperial ambitions.
- 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_69bd440e9d64819083e82cf33b4d9570 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:27 p.m.