Triple
T4339459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Combined Loyalist Military Command |
E97543
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | loyalist paramilitary coordinating body |
C859
|
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: loyalist paramilitary coordinating body Context triple: [Combined Loyalist Military Command, instanceOf, loyalist paramilitary coordinating body]
-
A.
paramilitary organization
chosen
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.
-
B.
Loyalist
A Loyalist is an individual who steadfastly supports and defends a person, group, cause, or authority, often prioritizing allegiance and stability over change or personal gain.
-
C.
clandestine group
A clandestine group is a secretive organization whose members covertly coordinate activities, often to pursue hidden political, criminal, or subversive objectives while avoiding detection by authorities or the public.
-
D.
Greek resistance organization
A Greek resistance organization is a clandestine group formed within Greece to oppose and undermine occupying or authoritarian regimes through coordinated political, military, and intelligence activities.
-
E.
paramilitary leader
A paramilitary leader is an individual who commands, organizes, and directs a non-regular, often politically motivated armed group that operates with military-style structure, tactics, and discipline outside or alongside official state forces.
- 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_69b3454662a481908fbcd0bbfaa3a0a4 |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:14 p.m.