Triple

T8630973
Position Surface form Disambiguated ID Type / Status
Subject A3ST E204399 entity
Predicate aircraftFlightRules P8780 FINISHED
Object IFR capable 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: IFR capable | Statement: [A3ST, aircraftFlightRules, IFR capable]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: aircraftFlightRules
Context triple: [A3ST, aircraftFlightRules, IFR capable]
  • 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. aviationAuthority
    Indicates that one entity serves as the official aviation regulatory or oversight body responsible for governing, certifying, or supervising the other entity’s aviation-related activities.
  • D. appliesToAirspaceOf
    Indicates that a rule, restriction, or condition is specifically relevant to, or in effect within, a particular airspace.
  • E. airworthinessStandard
    Indicates that something complies with the required safety and performance criteria to be considered fit and legal for operation in 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_69ca834b903c8190add96cc651e1a477 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc5730309081909a9a0256c9bf5f8f completed March 31, 2026, 11:22 p.m.
PD Predicate disambiguation batch_69cc455906f8819082edd79cb4a1cf28 completed March 31, 2026, 10:06 p.m.
Created at: March 30, 2026, 6:27 p.m.