Triple
T28437153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish resistance liaison missions |
E715298
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | clandestine military operation |
C340
|
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: clandestine military operation Context triple: [Polish resistance liaison missions, instanceOf, clandestine military operation]
-
A.
Cold War operation
A Cold War operation is a covert or overt mission conducted by a state or its proxies during the Cold War era to advance strategic, ideological, or geopolitical objectives without escalating into full-scale direct conflict between superpowers.
-
B.
military operation
chosen
A military operation is a coordinated and planned set of actions conducted by armed forces to achieve specific strategic, operational, or tactical objectives.
-
C.
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.
-
D.
militant operation
A militant operation is a coordinated, often clandestine action carried out by an organized armed group to achieve political, ideological, or territorial objectives through force or the threat of violence.
-
E.
covert intelligence operation
A covert intelligence operation is a secretive, state-directed activity designed to gather information or influence events without revealing the sponsor’s identity or involvement.
- 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_69efd6b253888190b3c7222ed6a403a8 |
completed | April 27, 2026, 9:35 p.m. |
Created at: April 28, 2026, 1:43 a.m.