Triple
T12054068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aviation Combat Element |
E286994
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military unit component |
C30365
|
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: military unit component Context triple: [Aviation Combat Element, instanceOf, military unit component]
-
A.
military unit
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
-
B.
component of land forces
A component of land forces is an organized, functionally distinct element of an army’s ground combat structure, such as infantry, armor, artillery, or support units, that contributes specific capabilities to land operations.
-
C.
military organization
A military organization is a structured group of armed forces personnel and resources, organized under a defined hierarchy and command system, to plan, coordinate, and conduct defense and combat operations in support of a state’s strategic objectives.
-
D.
Major Command Subordinate Unit
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.
-
E.
component of the United States Army
A component of the United States Army is a major organizational subdivision, such as the Active Army, Army National Guard, or Army Reserve, that collectively contributes to the Army’s overall mission and capabilities.
- F. None of above. chosen
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_69d6ab4780948190bdb9f7620c2ac27e |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:47 p.m.