Triple
T16757471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zentrum Cyber-Operationen |
E407245
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | militärische Dienststelle |
C298
|
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 Dienststelle Context triple: [Zentrum Cyber-Operationen, instanceOf, militärische Dienststelle]
-
A.
military establishment
A military establishment is an organized institution or network of institutions responsible for a nation's armed forces, defense policies, and related political, economic, and social interests.
-
B.
military administrative corps
A military administrative corps is a specialized branch of the armed forces responsible for managing personnel, logistics, finance, records, and other support functions that enable effective military operations.
-
C.
service branch of the Bundeswehr
A service branch of the Bundeswehr is a major organizational subdivision of Germany’s armed forces (such as the Army, Navy, or Air Force) that groups personnel, units, and capabilities according to their primary military function and domain of operations.
-
D.
military administrative division
A military administrative division is a geographically defined area organized under a specific command structure to manage, coordinate, and support military operations, logistics, and governance within its boundaries.
-
E.
military organization
chosen
A military organization is a structured group of armed forces personnel and resources, organized under a defined hierarchy and command system, to plan, coordinate, and conduct defense and combat operations in support of a state’s strategic 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_69d8839174188190909f190097207065 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:21 a.m.