Triple
T6502903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ministry of Ungentlemanly Warfare |
E148934
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | covert military organization |
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: covert military organization Context triple: [Ministry of Ungentlemanly Warfare, instanceOf, covert military 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.
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.
-
C.
covert intelligence organization
A covert intelligence organization is a secretive entity that gathers, analyzes, and acts on sensitive information through clandestine methods to influence or protect national or organizational interests.
-
D.
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.
-
E.
defense organization
A defense organization is an entity, typically governmental or intergovernmental, responsible for planning, coordinating, and executing activities to protect a nation or group of nations from military and security threats.
- 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_69c687e9ad288190bae5bcac9c8ac855 |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 1:42 p.m.