Triple
T6669545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orlik Aerobatic Team |
E151690
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Polish Air Force unit |
C21171
|
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: Polish Air Force unit Context triple: [Orlik Aerobatic Team, instanceOf, Polish Air Force unit]
-
A.
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.
-
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.
Luftwaffe wing
A Luftwaffe wing is a major operational air unit of the German Air Force, typically composed of several squadrons or groups equipped and organized to perform specific missions such as air defense, strike, or reconnaissance.
-
E.
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.
- 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_69c687f71fc081909dbd45d6377f6045 |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 2:02 p.m.