Triple
T27687334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kursk defensive operations |
E698066
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | defensive 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: defensive operation Context triple: [Kursk defensive operations, instanceOf, defensive operation]
-
A.
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.
-
B.
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.
-
C.
defensive play
Defensive play is a strategic approach in games or sports focused on preventing the opponent from scoring or gaining advantage, often by prioritizing protection, positioning, and risk minimization over aggressive advancement.
-
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.
defensive position
A defensive position is a strategically chosen and prepared location from which forces protect themselves and resist or repel an opponent’s attack.
- 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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
Created at: April 27, 2026, 2:50 p.m.