Triple
T33044806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Few |
E845564
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Royal Air Force personnel |
C60404
|
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 personnel Context triple: [The Few, instanceOf, Royal Air Force personnel]
-
A.
Royal Australian Air Force personnel
Individuals who serve or have served in the Royal Australian Air Force, fulfilling military, technical, and support roles in Australia's air and space defense forces.
-
B.
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.
-
C.
Royal Air Force signals unit
A Royal Air Force signals unit is a specialized military formation responsible for establishing, operating, and protecting communications and information systems that support RAF command, control, and operations.
-
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.
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.
- F. None of above. chosen
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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:24 a.m.