Triple
T2218174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish–Lithuanian intervention |
E48079
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | conflict in Eastern Europe |
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: conflict in Eastern Europe Context triple: [Polish–Lithuanian intervention, instanceOf, conflict in Eastern Europe]
-
A.
European war
A European war is a large-scale armed conflict primarily involving multiple nation-states within Europe, often driven by territorial, political, or ideological disputes that significantly reshape the continent’s balance of power.
-
B.
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.
-
C.
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.
-
D.
country in Eastern Europe
A country in Eastern Europe is a sovereign state located in the eastern part of the European continent, typically characterized by shared historical ties, cultural influences, and geopolitical connections within this region.
-
E.
guerrilla conflict
Guerrilla conflict is a form of irregular warfare in which small, mobile groups use hit-and-run tactics, ambushes, and sabotage to challenge a larger, conventionally organized force, often relying on local support and intimate knowledge of the terrain.
- 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_69a88aa1ee708190862c8c378c41e9eb |
completed | March 4, 2026, 7:40 p.m. |
Created at: March 4, 2026, 7:46 p.m.