Triple
T23927539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Home Defence 1940–1945 |
E602397
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Royal Air Force battle honour |
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 battle honour Context triple: [Home Defence 1940–1945, instanceOf, Royal Air Force battle honour]
-
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.
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 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.
-
D.
Royal Air Force senior staff position
A Royal Air Force senior staff position is a high-ranking leadership role responsible for directing major operational, strategic, or administrative functions within the RAF’s command structure.
-
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.
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_69e2953b928c819095395fa87baca583 |
completed | April 17, 2026, 8:16 p.m. |
Created at: April 17, 2026, 8:49 p.m.