Triple
T25855323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Britain battle honour |
E651326
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Royal Air Force campaign award |
C6399
|
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 campaign award Context triple: [Battle of Britain battle honour, instanceOf, Royal Air Force campaign award]
-
A.
British military award
chosen
A British military award is an official decoration or medal conferred by the United Kingdom to recognize acts of bravery, distinguished service, or long and meritorious conduct by members of the armed forces.
-
B.
major command of the Royal Air Force
A major command of the Royal Air Force is a high-level organizational formation responsible for directing and coordinating air operations, support, and resources within a defined functional or geographic area.
-
C.
Royal Air Force expeditionary air wing
A Royal Air Force expeditionary air wing is a deployable, self-contained air unit that combines aircraft, personnel, and support elements to conduct sustained air operations away from its home base.
-
D.
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.
-
E.
Royal Air Force aircraft variant
A Royal Air Force aircraft variant is a specific version of an aircraft type that has been modified or configured to meet particular operational, technical, or role-based requirements of the RAF.
- 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_69e7ab39035c8190be15c8aaee1bb858 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 8 a.m.