Triple
T35041195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Multi-National Division (South-East) (Iraq) |
E1011074
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | coalition military command |
C27150
|
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: coalition military command Context triple: [Multi-National Division (South-East) (Iraq), instanceOf, coalition military command]
-
A.
military operational command
A military operational command is an organizational entity responsible for planning, directing, coordinating, and controlling military forces and resources to achieve specific operational objectives within a defined area or mission scope.
-
B.
multinational military coalition
chosen
A multinational military coalition is a temporary or long-term alliance of armed forces from multiple sovereign states that coordinate resources, strategy, and operations to achieve shared security or defense objectives.
-
C.
central military command
A central military command is the highest-level organizational authority responsible for planning, directing, and coordinating the overall operations and strategy of a nation’s armed forces.
-
D.
joint command
A joint command is a unified military authority structure that coordinates and directs operations involving multiple service branches or allied forces to achieve common strategic objectives.
-
E.
coalition logistics framework
A coalition logistics framework is a structured model that coordinates and optimizes the planning, allocation, and movement of resources across multiple allied organizations to achieve shared operational 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_69f76dcea02c81908542a223f6d5059f |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.