Triple
T38283450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 11 Group operations network |
E1022138
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Royal Air Force operations network |
C47802
|
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 operations network Context triple: [No. 11 Group operations network, instanceOf, Royal Air Force operations network]
-
A.
Royal Air Force fighter tactic
A Royal Air Force fighter tactic is a coordinated set of maneuvers, formations, and engagement procedures designed to optimize RAF fighter aircraft effectiveness in air-to-air and air-to-ground combat operations.
-
B.
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.
-
C.
Royal Air Force signals unit
chosen
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 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.
-
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_69f76df0cddc81908d16c1556ff4097f |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.