Triple
T33968580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Combat Command B, 4th Armored Division |
E870926
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | maneuver element |
C37584
|
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: maneuver element Context triple: [Combat Command B, 4th Armored Division, instanceOf, maneuver element]
-
A.
military campaign maneuver
A military campaign maneuver is a coordinated movement or series of actions by armed forces designed to gain tactical or strategic advantage over an adversary within a broader operation or theater of war.
-
B.
MAGTF element
A MAGTF element is one of the four integrated components—command, ground combat, aviation combat, and logistics—that together form a Marine Air-Ground Task Force capable of conducting combined-arms operations.
-
C.
aerobatic maneuver
An aerobatic maneuver is a deliberate, controlled movement of an aircraft through three-dimensional space, often involving unusual attitudes or trajectories, performed for training, competition, or entertainment.
-
D.
offensive maneuver
An offensive maneuver is a deliberate tactical action aimed at gaining advantage over an opponent by aggressively advancing, attacking, or otherwise pressuring them.
-
E.
Operational formation
chosen
Operational formation is the structured arrangement and coordination of personnel, resources, and processes designed to execute specific tasks or missions efficiently within an operational context.
- 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_69f3499ce8e88190b66e1d49ad8c7037 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:50 a.m.