Triple

T32573329
Position Surface form Disambiguated ID Type / Status
Subject No. 316 (Polish) Squadron RAF E832573 entity
Predicate formedUnderCommandOf P200411 FINISHED
Object Royal Air Force NE NERFINISHED

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: Royal Air Force | Statement: [No. 316 (Polish) Squadron RAF, formedUnderCommandOf, Royal Air Force]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: formedUnderCommandOf
Context triple: [No. 316 (Polish) Squadron RAF, formedUnderCommandOf, Royal Air Force]
  • A. commissionedUnderCommandOf
    Indicates that an entity was formally authorized or initiated to act while under the authority or direction of a specific commanding entity.
  • B. commandedTo
    Indicates that one entity has issued an order or directive for another entity to perform a specific action or fulfill a particular duty.
  • C. commandedBy
    Indicates that one entity holds authoritative control or issues orders over another entity.
  • D. commandedIn
    Indicates that one entity held a position of command or leadership within a specified context, such as a battle, operation, or organization.
  • E. capturedUnderCommandOf
    Indicates that one entity was captured while operating under the authority, leadership, or command of another entity.
  • F. None of above. chosen

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_69f34927bb308190ad94da1b11cad13c completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69ff891e4b9c8190aa86a339a8944496 completed May 9, 2026, 7:21 p.m.
PD Predicate disambiguation batch_69ff8801180c8190b23e20996ca68e0a completed May 9, 2026, 7:16 p.m.
PDg Predicate description generation batch_69ff891d54248190be8742197564605a completed May 9, 2026, 7:21 p.m.
Created at: May 1, 2026, 1:04 a.m.