Triple

T30272936
Position Surface form Disambiguated ID Type / Status
Subject Martin XB-51 E769852 entity
Predicate competingAircraft P178325 FINISHED
Object English Electric Canberra 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: English Electric Canberra | Statement: [Martin XB-51, competingAircraft, English Electric Canberra]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: competingAircraft
Context triple: [Martin XB-51, competingAircraft, English Electric Canberra]
  • A. relatedAircraft
    Indicates that there is an association or connection between two aircraft, such as operational, functional, or contextual relatedness.
  • B. referredAircraftConflict
    Indicates that there is a potential or actual conflict involving an aircraft that has been referenced or designated in the current context.
  • C. opposedAircraftInServiceWith
    Indicates that one aircraft was in active service with a party that was in opposition to the party operating the other aircraft.
  • D. opponentAircraft
    Indicates that one aircraft is an adversary or opposing aircraft relative to another in a conflict or competitive context.
  • E. successorAircraft
    Indicates that one aircraft model directly follows and replaces another in a developmental or operational sequence.
  • 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_69f224856d9881908c7f0dd64f059672 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f70e8755a48190931eaa77946f9460 completed May 3, 2026, 8:59 a.m.
PD Predicate disambiguation batch_69f70abc00848190a1c3f495ef6c8dc6 completed May 3, 2026, 8:43 a.m.
PDg Predicate description generation batch_69f70e854b9c8190a3416e2189e17742 completed May 3, 2026, 8:59 a.m.
Created at: April 29, 2026, 7:44 p.m.