Triple
T32595198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | joint special operations task group |
E833183
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | joint force |
C43630
|
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: joint force Context triple: [joint special operations task group, instanceOf, joint force]
-
A.
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.
-
B.
belligerent force
A belligerent force is an organized military or armed group that actively participates in hostilities during an armed conflict.
-
C.
regional joint task force
A regional joint task force is a collaborative, multi-agency or multi-national organization formed within a specific geographic area to coordinate and execute integrated operations toward shared security, emergency response, or policy objectives.
-
D.
multinational military coalition
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.
-
E.
joint organization
chosen
A joint organization is a collaborative entity formed by two or more independent parties that share resources, responsibilities, and decision-making to achieve common 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_69f34929ff648190aded9424aa7564ae |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1:05 a.m.