Triple
T31223226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Standing Joint Force Headquarters |
E796070
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | joint command element |
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 command element Context triple: [Standing Joint Force Headquarters, instanceOf, joint command element]
-
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.
commander
A commander is a leader who directs and coordinates the actions of others, typically within a military or organized group, to achieve strategic objectives.
-
C.
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.
-
D.
bilateral command
A bilateral command is an instruction or directive that involves or requires coordinated action, agreement, or communication between two distinct parties or sides.
-
E.
mission commander
A mission commander is the individual responsible for planning, directing, and overseeing the successful execution and safety of an entire mission and its team.
- 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_69f224da98f88190ab32f690cce5d303 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:10 p.m.