Triple
T11923034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alekseyev Organization |
E283705
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military-political organization |
C8130
|
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-political organization Context triple: [Alekseyev Organization, instanceOf, military-political organization]
-
A.
military organization
A military organization is a structured group of armed forces personnel and resources, organized under a defined hierarchy and command system, to plan, coordinate, and conduct defense and combat operations in support of a state’s strategic objectives.
-
B.
military political organ
chosen
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.
-
C.
political organization
A political organization is a structured group of individuals who collectively pursue specific political goals, such as influencing public policy, gaining or maintaining power, or representing particular interests within a political system.
-
D.
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.
-
E.
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.
- 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_69d6ab2ce9c48190b5d39511b524f666 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:45 p.m.