Triple
T37232908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kampfeinsitzerkommando Boelcke |
E923188
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War I German fighter unit |
C36123
|
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: World War I German fighter unit Context triple: [Kampfeinsitzerkommando Boelcke, instanceOf, World War I German fighter unit]
-
A.
World War I aviation unit
chosen
A World War I aviation unit is a military organization composed of aircraft, aircrew, and support personnel tasked with conducting aerial operations such as reconnaissance, air combat, and ground attack during the First World War.
-
B.
Luftwaffe fighter unit
A Luftwaffe fighter unit is a World War II-era German air force formation composed of fighter aircraft and their crews, organized to achieve air superiority, escort missions, and defensive operations.
-
C.
World War I air unit
A World War I air unit is a military formation composed of early aircraft and their crews, organized to conduct reconnaissance, air combat, and ground-attack missions during the First World War.
-
D.
German fighter squadron
A German fighter squadron is a military aviation unit composed of multiple fighter aircraft and their pilots, organized to conduct air-to-air and air-to-ground combat missions under a unified command structure.
-
E.
German military aviation unit
A German military aviation unit is an organized formation within Germany’s armed forces that operates, maintains, and supports aircraft to conduct air missions for defense, reconnaissance, transport, and combat operations.
- 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_69f76ea7f0008190b31b8e30f3d05a71 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:15 p.m.