Triple
T3807073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theater Special Operations Commands |
E93033
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subordinate unified commands |
C12885
|
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: subordinate unified commands Context triple: [Theater Special Operations Commands, instanceOf, subordinate unified commands]
-
A.
subordinate unified combatant command
chosen
A subordinate unified combatant command is a command established by a unified combatant command to conduct operations on a continuing basis within a specific functional or geographic area under the authority of that parent unified command.
-
B.
major command echelon
A major command echelon is a high-level organizational tier within a military or large institution that oversees multiple subordinate units and directs strategic operations, resources, and policies across a broad mission area.
-
C.
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.
-
D.
theatre command
Theatre command is a high-level military headquarters responsible for planning, directing, and coordinating operations across a broad geographic area or theater of war.
-
E.
military administrative division
A military administrative division is a geographically defined area organized under a specific command structure to manage, coordinate, and support military operations, logistics, and governance within its boundaries.
- 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_69aed96a60088190ab1df8390fffc935 |
completed | March 9, 2026, 2:30 p.m. |
Created at: March 9, 2026, 3:16 p.m.