Triple
T2931457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pro-Treaty forces |
E78964
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | belligerent in civil war |
C6037
|
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: belligerent in civil war Context triple: [Pro-Treaty forces, instanceOf, belligerent in civil war]
-
A.
belligerent in war
A belligerent in war is a state or organized party that is legally recognized as actively engaged in armed conflict, possessing rights and obligations under the laws of war.
-
B.
side in civil conflict
chosen
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.
-
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.
co-belligerent state
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.
-
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_69ad8b0d40b481908bc2a5fa2e73c3fb |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 2:55 p.m.