Triple
T23224892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 45 Squadron Indian Air Force |
E580987
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indian Air Force squadron |
C38825
|
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: Indian Air Force squadron Context triple: [No. 45 Squadron Indian Air Force, instanceOf, Indian Air Force squadron]
-
A.
Indian Air Force unit
An Indian Air Force unit is an organized formation of personnel, aircraft, and support resources structured to conduct specific air and space operations, training, or support functions within the Indian Air Force.
-
B.
Air Force squadron
chosen
An Air Force squadron is a military aviation unit composed of multiple aircraft and personnel, organized to perform specific operational, training, or support missions under a unified command.
-
C.
aviation regiment
An aviation regiment is a military unit composed of multiple aircraft squadrons or flights, along with their supporting personnel and equipment, organized to conduct coordinated air operations.
-
D.
Royal Flying Corps squadron
A Royal Flying Corps squadron is a military aviation unit of the British Army’s pre-1918 air arm, typically composed of multiple aircraft, aircrew, and ground personnel organized for reconnaissance, combat, and support operations during World War I.
-
E.
Royal Air Force squadron
A Royal Air Force squadron is a military aviation unit comprising aircraft, aircrew, and support personnel organized under a specific command structure to perform designated operational, training, or support roles.
- 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_69e246043c48819089bae72c9a9c306c |
completed | April 17, 2026, 2:39 p.m. |
Created at: April 17, 2026, 4:08 p.m.