Triple
T11561360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fourth Air Force |
E274150
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | major subordinate unit |
C14560
|
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 subordinate unit Context triple: [Fourth Air Force, instanceOf, major subordinate unit]
-
A.
Major Command Subordinate Unit
chosen
A Major Command Subordinate Unit is an organizational entity that operates under a major command, executing its directives and managing assigned missions, resources, and personnel within a defined scope of responsibility.
-
B.
subordinate organization
A subordinate organization is an entity that operates under the authority, control, or oversight of a higher-level organization, carrying out specific functions or responsibilities delegated to it.
-
C.
subordinate unified combatant command
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.
-
D.
subordinate office
A subordinate office is an administrative unit that operates under the authority and direction of a higher-level office, carrying out delegated tasks and supporting its functions.
-
E.
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.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:37 p.m.