Triple
T30022424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turkish National Forces |
E762782
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | irregular military organization |
C30016
|
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: irregular military organization Context triple: [Turkish National Forces, instanceOf, irregular military organization]
-
A.
irregular military forces
chosen
Irregular military forces are non-state or semi-organized armed groups that operate outside formal national military structures, often using unconventional tactics and lacking official recognition as regular armed forces.
-
B.
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.
-
C.
rebel group military formation
A rebel group military formation is an organized, non-state armed unit structured to conduct coordinated combat or insurgent operations against established authorities or rival forces.
-
D.
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.
-
E.
alliance of armed groups
An alliance of armed groups is a cooperative association of distinct militant or paramilitary organizations that coordinate strategies, resources, and operations to pursue shared political, ideological, or territorial objectives.
- 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_69f2246ee6e48190b69e837b913b398a |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:47 p.m.