Triple
T13040907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 312 (Czechoslovak) Squadron RAF |
E327187
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Royal Air Force fighter squadron |
C4815
|
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 fighter squadron Context triple: [No. 312 (Czechoslovak) Squadron RAF, instanceOf, Royal Air Force fighter squadron]
-
A.
Royal Air Force squadron
chosen
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.
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.
-
D.
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.
-
E.
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.
- 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_69d8076e64308190904fb5c93517c901 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 8:56 p.m.