Triple
T21887531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 663 Squadron AAC |
E540445
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British Army Air Corps unit |
C45468
|
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: British Army Air Corps unit Context triple: [No. 663 Squadron AAC, instanceOf, British Army Air Corps unit]
-
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 Australian Air Force unit
A Royal Australian Air Force unit is an organizational entity within the RAAF, composed of personnel, aircraft, and equipment structured to perform specific operational, training, or support roles in air and space power.
-
D.
branch of the Royal Air Force
A branch of the Royal Air Force is a major organizational subdivision responsible for a specific functional area of air and space operations, support, or administration within the RAF.
-
E.
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.
- 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_69e0c47a95908190ae3e19b716accb3d |
completed | April 16, 2026, 11:14 a.m. |
Created at: April 16, 2026, 7:05 p.m.