Triple

T6076373
Position Surface form Disambiguated ID Type / Status
Subject Air Officer Commanding No. 3 Group RAF E135409 entity
Predicate historicalSubordination P8011 FINISHED
Object Air Officer Commanding-in-Chief Bomber Command E232800 NE FINISHED

How this triple was built (3 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Air Officer Commanding-in-Chief Bomber Command | Statement: [Air Officer Commanding No. 3 Group RAF, historicalSubordination, Air Officer Commanding-in-Chief Bomber Command]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Air Officer Commanding-in-Chief Bomber Command
Context triple: [Air Officer Commanding No. 3 Group RAF, historicalSubordination, Air Officer Commanding-in-Chief Bomber Command]
  • A. Air Officer Commanding-in-Chief Bomber Command chosen
    The Air Officer Commanding-in-Chief Bomber Command was the senior Royal Air Force post responsible for directing Britain's strategic bombing operations, particularly during the Second World War.
  • B. Air Officer Commanding-in-Chief Fighter Command
    The Air Officer Commanding-in-Chief Fighter Command was the senior Royal Air Force post responsible for directing Britain's fighter air defence, notably during the early years of the Second World War.
  • C. Air Officer Commanding No. 11 Group RAF
    Air Officer Commanding No. 11 Group RAF was a senior Royal Air Force command role responsible for overseeing one of the RAF’s key operational groups, particularly noted for its air defence responsibilities.
  • D. Air Commander-in-Chief Allied Expeditionary Air Force
    The Air Commander-in-Chief Allied Expeditionary Air Force was the senior operational command responsible for coordinating and directing Allied air operations in support of the D-Day landings and subsequent campaigns in Northwest Europe during World War II.
  • E. Air Officer Commanding No. 3 Group RAF
    Air Officer Commanding No. 3 Group RAF was a senior Royal Air Force command role responsible for overseeing the operations and administration of No. 3 Group, a major formation within RAF Bomber and later Strike Commands.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalSubordination
Context triple: [Air Officer Commanding No. 3 Group RAF, historicalSubordination, Air Officer Commanding-in-Chief Bomber Command]
  • A. historicalSubunit chosen
    Indicates that one entity functioned as a subordinate or component part of another entity during a specific historical period, but is no longer in that role in the present.
  • B. subordinateTo
    Indicates that one entity holds a lower rank, status, or authority and is subject to the control, direction, or oversight of another entity.
  • C. historicalForm
    Indicates that one entity is an earlier or historically attested form or variant of another entity.
  • D. historicallyEncompassed
    Indicates that one entity previously included, covered, or contained another entity within its scope, extent, or boundaries during a past historical period.
  • E. historicallyImposed
    Indicates that one entity has enforced, established, or applied something upon another in the past, typically through authority, power, or institutional action.
  • F. None of above.

Provenance (4 batches)

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_69c0087ad31c8190ab936e0ff28614b6 completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c0575ec63081908a868a41855acf73 completed March 22, 2026, 8:55 p.m.
NED1 Entity disambiguation (via context triple) batch_69c11d43f7908190845c2337cd243a3c completed March 23, 2026, 11 a.m.
PD Predicate disambiguation batch_69c049f21fe08190995df3c5c05fb8ea completed March 22, 2026, 7:58 p.m.
Created at: March 22, 2026, 4:11 p.m.