Triple

T19725307
Position Surface form Disambiguated ID Type / Status
Subject Strike Fighter Wing Atlantic E473710 entity
Predicate aircraftTypeManaged P137089 FINISHED
Object strike fighter aircraft 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: strike fighter aircraft | Statement: [Strike Fighter Wing Atlantic, aircraftTypeManaged, strike fighter aircraft]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: aircraftTypeManaged
Context triple: [Strike Fighter Wing Atlantic, aircraftTypeManaged, strike fighter aircraft]
  • A. aircraftType
    Indicates the specific model or category of aircraft associated with an entity or event.
  • B. aircraftTypeMaintained
    Indicates that a maintenance entity performs or is responsible for maintaining a specific type of aircraft.
  • C. iataAircraftTypeCode
    Indicates the standardized IATA code that specifies the aircraft type used in a flight or aviation context.
  • D. poweredAircraftType
    Indicates that one entity is a type or category of aircraft that is propelled by an onboard power source (e.g., engines), as opposed to being unpowered.
  • E. usedByAircraftType
    Indicates that something (such as equipment, infrastructure, or a procedure) is employed or operated by a specific type or category of aircraft.
  • 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_69d8e517ebd48190979ee76723bcfadf completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e649f7bedc81908f784832c0fc10a1 completed April 20, 2026, 3:44 p.m.
PD Predicate disambiguation batch_69e5304a7aac8190ac13f75f0c008e45 completed April 19, 2026, 7:43 p.m.
PDg Predicate description generation batch_69e532bbedf081908d801600e2af94a7 completed April 19, 2026, 7:53 p.m.
Created at: April 10, 2026, 1:46 p.m.