Triple
T8588603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Command Support Base |
E203371
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | branch of the Swiss Army |
C24685
|
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: branch of the Swiss Army Context triple: [Command Support Base, instanceOf, branch of the Swiss Army]
-
A.
branch of the German Army
A branch of the German Army is a specialized organizational subdivision responsible for a distinct set of military functions, capabilities, and operational roles within the overall land forces structure.
-
B.
branch of the Bundeswehr
A branch of the Bundeswehr is a major organizational component of Germany’s armed forces, such as the Army, Navy, or Air Force, each with distinct roles, capabilities, and responsibilities in national defense.
-
C.
arms manufacturer
An arms manufacturer is a company or entity that designs, produces, and supplies weapons, ammunition, and related military equipment for use by armed forces, security agencies, or private clients.
-
D.
recoilless rifle variant
A recoilless rifle variant is a modified form of a recoilless gun designed to launch projectiles with minimal recoil, typically through specialized venting or counter-mass systems, for use in portable or vehicle-mounted anti-armor or support roles.
-
E.
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.
- F. None of above. chosen
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_69ca8329bb7c8190a63c643730839103 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:23 p.m.