Triple
T14079278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royalist cause in the English Civil War |
E338821
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | belligerent in a 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 a civil war Context triple: [Royalist cause in the English Civil War, instanceOf, belligerent in a 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.
belligerent force
A belligerent force is an organized military or armed group that actively participates in hostilities during an armed conflict.
-
C.
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.
-
D.
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.
-
E.
civil war battle
A civil war battle is an armed conflict between organized factions within the same country, typically involving large-scale military engagements over political, territorial, or ideological control.
- 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_69d81c687b0c819087fd9ed4198403f8 |
completed | April 9, 2026, 9:38 p.m. |
Created at: April 9, 2026, 10:21 p.m.