Triple
T14786227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CJOC |
E347532
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | joint operations command |
C8007
|
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 operations command Context triple: [CJOC, instanceOf, joint operations command]
-
A.
joint command
chosen
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.
military special operations command
A military special operations command is a specialized organizational unit responsible for planning, directing, and executing high-risk, strategically critical missions using elite, highly trained forces.
-
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.
United States military command
The United States military command is the hierarchical structure of authority and control through which national defense policies and military operations are directed, coordinated, and executed across all branches of the U.S. Armed Forces.
-
E.
military operations center
A military operations center is a centralized facility where commanders and staff monitor, coordinate, and direct military activities and resources in real time.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:31 a.m.