Triple

T7769312
Position Surface form Disambiguated ID Type / Status
Subject No. 141 Squadron RAF E179028 entity
Predicate notableAircraftFeature P65000 FINISHED
Object turret-armed fighter 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: turret-armed fighter | Statement: [No. 141 Squadron RAF, notableAircraftFeature, turret-armed fighter]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: notableAircraftFeature
Context triple: [No. 141 Squadron RAF, notableAircraftFeature, turret-armed fighter]
  • A. referredAircraftNotableFeature chosen
    Indicates that a referenced aircraft is associated with a notable or distinguishing feature.
  • B. notableAircraftUsed
    Indicates that an entity is known for using, operating, or being associated with a particular aircraft in a notable or significant way.
  • C. notableAircraftRole
    Indicates that an aircraft is notably associated with performing a particular role or function.
  • D. notableAircraftPowered
    Indicates that an aircraft is notably powered or propelled by a specified engine, powerplant, or propulsion system.
  • E. notableTransportAircraft
    Indicates that the subject is a transport aircraft recognized for particular significance, such as historical importance, performance, or impact on aviation.
  • 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_69c69f30602c819082ab52cd4af5c592 completed March 27, 2026, 3:16 p.m.
NER Named-entity recognition batch_69c704376dc08190890f5ebb9f259cfd completed March 27, 2026, 10:27 p.m.
PD Predicate disambiguation batch_69c7016f4ce881909c2e9f610255187b completed March 27, 2026, 10:15 p.m.
Created at: March 27, 2026, 4:11 p.m.