Triple
T24911666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Freedom Deal |
E623861
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. bombing campaign |
C179
|
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: U.S. bombing campaign Context triple: [Operation Freedom Deal, instanceOf, U.S. bombing campaign]
-
A.
strategic bombing campaign
chosen
A strategic bombing campaign is a sustained aerial offensive aimed at weakening an enemy’s war-making capacity and morale by targeting key industrial, military, and infrastructural assets rather than solely engaging frontline forces.
-
B.
United States special forces raid
A United States special forces raid is a highly planned, time-sensitive military operation conducted by elite U.S. units to infiltrate hostile or denied areas, achieve a specific objective such as capturing or killing high-value targets, and exfiltrate rapidly with minimal collateral damage.
-
C.
scorched-earth campaign
A scorched-earth campaign is a ruthless strategy in which a party deliberately destroys resources, infrastructure, or reputations to deny advantages to an opponent, even at great cost to themselves.
-
D.
Strategic bombing force
A strategic bombing force is a military aviation unit organized, equipped, and trained to conduct long-range, high-impact bombing campaigns against an adversary’s critical infrastructure, industry, and strategic assets to weaken their capacity and will to wage war.
-
E.
naval bombardment
Naval bombardment is the use of warships’ long-range weapons to attack targets on land or at sea, typically to weaken enemy defenses, infrastructure, or forces.
- 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_69e2fac889c081908e9ff686cb428e5a |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 5:28 a.m.