Triple
T21188181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 63 Squadron RAF Regiment |
E522140
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | RAF Regiment squadron |
C13117
|
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: RAF Regiment squadron Context triple: [No. 63 Squadron RAF Regiment, instanceOf, RAF Regiment squadron]
-
A.
Royal Air Force Regiment squadron
chosen
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.
-
B.
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.
-
C.
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.
-
D.
Air Force squadron
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.
-
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.
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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 3:07 p.m.