Triple

T2229338
Position Surface form Disambiguated ID Type / Status
Subject Class A airspace E48727 entity
Predicate primaryRulesOfFlight P8780 FINISHED
Object Instrument Flight Rules 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: Instrument Flight Rules | Statement: [Class A airspace, primaryRulesOfFlight, Instrument Flight Rules]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: primaryRulesOfFlight
Context triple: [Class A airspace, primaryRulesOfFlight, Instrument Flight Rules]
  • A. flightRules chosen
    Indicates the regulatory or procedural rules that govern how a flight must be conducted or operated.
  • B. flightRegime
    Indicates the operational conditions or phase of flight under which an aircraft or aerospace vehicle is functioning (e.g., speed, altitude, and atmospheric regime).
  • C. controlsPhaseOfFlight
    Indicates that one entity has authority over or manages a specific phase of another entity’s flight operation.
  • D. primaryAircraftRole
    Indicates the main operational function or mission type an aircraft is primarily designed or used to perform.
  • E. flyByWire
    Indicates a control relationship where an aircraft’s control surfaces are operated by electronic signals rather than direct mechanical linkage from the pilot.
  • 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_69a88aa51b388190949868ec9766e587 completed March 4, 2026, 7:40 p.m.
NER Named-entity recognition batch_69abc0685b688190857a76c1043f4b92 completed March 7, 2026, 6:06 a.m.
PD Predicate disambiguation batch_69abbdadbb0c8190b3a1ede31b8acbfa completed March 7, 2026, 5:54 a.m.
Created at: March 4, 2026, 7:47 p.m.