Triple
T15772085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFNORTH |
E382386
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | major command-level organization |
C6110
|
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: major command-level organization Context triple: [AFNORTH, instanceOf, major command-level organization]
-
A.
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.
-
B.
major field command
chosen
A major field command is a high-level military organizational unit responsible for directing, coordinating, and sustaining operations across a broad geographic area or functional domain within a nation's armed forces.
-
C.
major operational formation
A major operational formation is a large, organized military force grouping (such as an army, corps, or equivalent) designed to conduct sustained, coordinated operations within a theater of war.
-
D.
administrative command
An administrative command is a privileged instruction or operation executed within a system to configure, control, or manage resources, users, and security settings beyond the capabilities of regular users.
-
E.
branch-level command
A branch-level command is an instruction or directive executed within the context of a specific branch (such as in version control or organizational hierarchy), affecting only that branch’s state, behavior, or data.
- 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_69d86da09a10819082fe9797b23e4664 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:47 a.m.