Triple
T18151880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schlacht bei Kay |
E434523
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Militärische Auseinandersetzung |
C7050
|
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: Militärische Auseinandersetzung Context triple: [Schlacht bei Kay, instanceOf, Militärische Auseinandersetzung]
-
A.
military confrontation
chosen
A military confrontation is an armed clash between organized state or non-state forces, involving the use or threat of force to achieve political, territorial, or strategic objectives.
-
B.
covert military conflict
A covert military conflict is a hidden or plausibly deniable struggle between states or organized groups that uses clandestine operations, proxies, and intelligence activities instead of overt, declared warfare.
-
C.
Einrichtung der Bundeswehr
Eine Einrichtung der Bundeswehr ist eine ortsfeste militärische oder zivile Organisationseinheit der deutschen Streitkräfte, die spezifische Aufgaben wie Ausbildung, Logistik, Verwaltung, Forschung oder Versorgung zur Unterstützung des militärischen Auftrags wahrnimmt.
-
D.
guerrilla conflict
Guerrilla conflict is a form of irregular warfare in which small, mobile groups use hit-and-run tactics, ambushes, and sabotage to challenge a larger, conventionally organized force, often relying on local support and intimate knowledge of the terrain.
-
E.
armed confrontation
Armed confrontation is a hostile encounter between opposing parties in which participants use or threaten to use weapons to achieve conflicting objectives.
- 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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:29 a.m.