Triple

T5509712
Position Surface form Disambiguated ID Type / Status
Subject Air Officer Commanding No. 205 Group RAF E144531 entity
Predicate associatedUnitRole P40371 FINISHED
Object strategic bombing operations LITERAL FINISHED

How this triple was built (2 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: strategic bombing operations | Statement: [Air Officer Commanding No. 205 Group RAF, associatedUnitRole, strategic bombing operations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: associatedUnitRole
Context triple: [Air Officer Commanding No. 205 Group RAF, associatedUnitRole, strategic bombing operations]
  • A. associatedUnitType
    Indicates that one entity is linked to or characterized by a particular type or category of unit.
  • B. associatedWithUnit
    Indicates that one entity has a connection, linkage, or affiliation with a particular unit (such as a division, department, or organizational subunit).
  • C. unitRole chosen
    Indicates the functional role or purpose that a unit serves within a larger system or context.
  • D. associatedWithStationRole
    Indicates that an entity has a connection or involvement with a specific role or function at a station.
  • E. allianceRole
    Indicates the specific function, status, or responsibility an entity holds within an alliance or cooperative partnership.
  • F. None of above.

Provenance (3 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_69c008f6b5048190a09064116062cf69 completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c01f4ba90c8190ad22e5de84c545f9 completed March 22, 2026, 4:56 p.m.
PD Predicate disambiguation batch_69c01b07bde08190b3933b96bdc70dd5 completed March 22, 2026, 4:38 p.m.
Created at: March 22, 2026, 3:33 p.m.