Triple
T31037837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dodge City War |
E790898
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | political and law-enforcement conflict |
C51986
|
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: political and law-enforcement conflict Context triple: [Dodge City War, instanceOf, political and law-enforcement conflict]
-
A.
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.
-
B.
constitutional conflict
A constitutional conflict is a dispute arising when different branches or levels of government, or competing legal interpretations, clash over the meaning, application, or limits of constitutional authority.
-
C.
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.
-
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.
political power struggle
chosen
A political power struggle is a dynamic conflict in which individuals or groups compete to gain, maintain, or expand control over political authority, resources, and decision-making.
- 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_69f224c97a788190b5da1ead6038a74e |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:59 p.m.