Triple
T8926347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Britain airfields |
E212547
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Royal Air Force infrastructure |
C12091
|
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 infrastructure Context triple: [Battle of Britain airfields, instanceOf, Royal Air Force infrastructure]
-
A.
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.
-
B.
Royal Air Force related topic
chosen
A Royal Air Force related topic is any subject, concept, event, unit, technology, or individual directly connected to the history, operations, organization, culture, or impact of the United Kingdom’s air and space warfare service branch.
-
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 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.
-
E.
British Army facility
A British Army facility is a location owned, operated, or used by the British Army for purposes such as training, administration, logistics, accommodation, storage, or operational deployment.
- 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_69ca839481d48190b42b037e0d0f636c |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 6:57 p.m.