Triple
T30631200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union Solidarity and Development Party |
E779716
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military-backed political party |
C57743
|
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: military-backed political party Context triple: [Union Solidarity and Development Party, instanceOf, military-backed political party]
-
A.
armed wing of political party
An armed wing of a political party is a militarized or paramilitary organization formally or informally linked to a political party, using or preparing to use force to advance the party’s political objectives.
-
B.
communist military organization
A communist military organization is an armed group structured under communist ideology, aiming to defend, expand, or enforce a socialist or communist political system through organized military means.
-
C.
paramilitary organization
A paramilitary organization is a structured group that operates with military-style training, hierarchy, and tactics but is not formally part of a recognized state's official armed forces.
-
D.
military political organ
A military political organ is an institutional body within the armed forces responsible for overseeing political education, ideological control, and party or state loyalty among military personnel.
-
E.
former rebel movement
A former rebel movement is an organized group that previously engaged in armed or political resistance against an established authority but has since ceased such activities, often transitioning into a political, social, or demobilized entity.
- F. None of above. chosen
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_69f224a431548190a44ad9d088dbf91f |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:28 p.m.