Triple
T554392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Auxiliary Air Force |
E11910
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | component of the Royal Air Force |
C2925
|
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: component of the Royal Air Force Context triple: [Royal Auxiliary Air Force, instanceOf, component of the Royal Air Force]
-
A.
component of the French Air and Space Force
A component of the French Air and Space Force is an organizational subdivision, such as a command, unit, or formation, that performs specific operational, support, or administrative functions within France’s air and space defense structure.
-
B.
Luftwaffe bomber wing
A Luftwaffe bomber wing is a large, operational German air force unit composed of multiple bomber groups, responsible for planning and executing coordinated bombing missions.
-
C.
aerial warfare service branch
chosen
An aerial warfare service branch is a military organization responsible for conducting and supporting combat and operational activities in the air and, increasingly, in space and cyberspace domains.
-
D.
Allied air force
Allied air force: The collective aerial military forces of nations united in a coalition, coordinating air operations to achieve shared strategic and tactical objectives in conflict.
-
E.
British Army organizational element
A British Army organizational element is a defined structural unit—such as a section, platoon, company, battalion, brigade, or division—comprising personnel, equipment, and command relationships arranged to perform specific military roles within the Army’s hierarchy.
- 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_69a4932941d08190815efd422f0b4ca7 |
completed | March 1, 2026, 7:27 p.m. |
Created at: March 1, 2026, 7:32 p.m.