Triple
T8588643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Logistics Base of the Armed Forces |
E203372
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Swiss Armed Forces unit |
C2497
|
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: Swiss Armed Forces unit Context triple: [Logistics Base of the Armed Forces, instanceOf, Swiss Armed Forces unit]
-
A.
military unit
chosen
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
-
B.
Belgian Air Force unit
A Belgian Air Force unit is an organizational entity within the Belgian Air Component responsible for executing specific air defense, support, training, or operational missions using assigned personnel, aircraft, and equipment.
-
C.
Belgian Air Force unit
A Belgian Air Force unit is an organizational subdivision of the Belgian Air Component, composed of personnel, aircraft, and equipment structured to perform specific operational, training, or support missions within national and allied defense frameworks.
-
D.
paratrooper unit
A paratrooper unit is a specialized military formation trained and equipped to deploy from aircraft by parachute to conduct airborne assaults, rapid insertions, and operations behind enemy lines.
-
E.
parachute infantry regiment
A parachute infantry regiment is a military unit composed of soldiers trained and equipped to deploy by parachute into combat zones to conduct airborne assault, seizure, and holding of key objectives behind enemy lines.
- 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_69ca8329bb7c8190a63c643730839103 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:23 p.m.