Triple
T9066660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Village guard system (Turkey) |
E217261
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | counterinsurgency auxiliary force |
C21918
|
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: counterinsurgency auxiliary force Context triple: [Village guard system (Turkey), instanceOf, counterinsurgency auxiliary force]
-
A.
auxiliary military force
chosen
An auxiliary military force is a supplementary, often non-regular or part-time armed organization that supports a nation’s primary military through additional manpower, specialized skills, or local defense roles.
-
B.
occupation force
An occupation force is a military presence deployed by a controlling power to maintain authority, security, and administration over a captured or foreign territory.
-
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.
special operations forces unit
A special operations forces unit is a highly trained, small military team designed to conduct specialized, high-risk missions such as reconnaissance, direct action, counterterrorism, and unconventional warfare, often in politically sensitive or denied environments.
-
E.
special operations support unit
A special operations support unit is a specialized organization that provides logistical, intelligence, technical, and operational assistance to special operations forces to enable and sustain their missions.
- 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_69ca83d5a7f48190b16c1e59bd43ede0 |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:11 p.m.