Triple
T29793785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CIMIC |
E756483
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | civil-military cooperation doctrine |
C18880
|
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: civil-military cooperation doctrine Context triple: [CIMIC, instanceOf, civil-military cooperation doctrine]
-
A.
civil–military relations concept
A civil–military relations concept explains how political authorities and military institutions interact, share power, and maintain control to balance security needs with democratic governance and societal values.
-
B.
civil-military coordination structure
chosen
A civil-military coordination structure is an organized framework that defines roles, processes, and communication channels between civilian authorities and military forces to plan, manage, and execute joint operations effectively and lawfully.
-
C.
military organizational doctrine
Military organizational doctrine is the formalized set of principles, structures, and procedures that guide how armed forces are organized, coordinated, and employed to achieve strategic and operational objectives.
-
D.
military doctrinal framework
A military doctrinal framework is a structured set of principles, concepts, and guidelines that shapes how armed forces plan, organize, and conduct operations across different levels of war.
-
E.
military doctrine handbook
A military doctrine handbook is an authoritative manual that outlines the fundamental principles, strategies, tactics, and procedures guiding the planning and conduct of military operations.
- 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_69f22454583081908927516cb9938d1d |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 5:14 p.m.