Triple
T23955426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 135 EAW |
E603774
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Royal Air Force expeditionary air wing |
C48707
|
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: Royal Air Force expeditionary air wing Context triple: [135 EAW, instanceOf, Royal Air Force expeditionary air wing]
-
A.
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.
-
B.
Royal Air Force Regiment squadron
A Royal Air Force Regiment squadron is a specialized ground combat and force protection unit of the RAF responsible for defending airfields, aircraft, and related assets through infantry, air defense, and security operations.
-
C.
Royal Air Force operational conversion unit
A Royal Air Force operational conversion unit is a training formation that transitions qualified aircrew onto specific aircraft types and prepares them for front-line operational roles.
-
D.
Royal Air Force maintenance unit
A Royal Air Force maintenance unit is a specialized organizational entity responsible for the inspection, repair, servicing, and logistical support of RAF aircraft and related equipment to ensure operational readiness and safety.
-
E.
Fleet Air Arm squadron
A Fleet Air Arm squadron is a naval aviation unit of the British Royal Navy responsible for operating and maintaining aircraft in support of maritime and joint operations.
- 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_69e2954222288190a7323554d0cca8d7 |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 17, 2026, 9:21 p.m.