Triple
T36974720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 21 Squadron SAAF |
E914666
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | squadron of the South African Air Force |
C28649
|
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: squadron of the South African Air Force Context triple: [21 Squadron SAAF, instanceOf, squadron of the South African Air Force]
-
A.
squadron
chosen
A squadron is an organized military unit, typically consisting of a group of aircraft, ships, or soldiers, commanded as a single tactical formation.
-
B.
Commonwealth air force squadron
A Commonwealth air force squadron is a military aviation unit from a nation within the Commonwealth of Nations, typically comprising aircraft, aircrew, and support personnel organized for operational, training, or support missions under a unified command structure.
-
C.
Air Force of Zimbabwe unit
An Air Force of Zimbabwe unit is an organizational subdivision of the Air Force of Zimbabwe, comprising personnel, aircraft, and equipment structured to perform specific operational, support, or training functions within the national air defense framework.
-
D.
Royal New Zealand Air Force squadron
A Royal New Zealand Air Force squadron is a military aviation unit of the RNZAF, typically comprising aircraft, aircrew, and support personnel organized to perform specific operational, training, or support roles.
-
E.
fighter squadron
A fighter squadron is a military aviation unit composed of multiple fighter aircraft and their personnel, organized to conduct air-to-air and air-to-ground combat missions under a unified command.
- 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_69f76e8d13b4819089af24a47ce092fc |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.