Triple

T17943216
Position Surface form Disambiguated ID Type / Status
Subject SU95 E448635 entity
Predicate aircraftIcaoCodeScope P16898 FINISHED
Object used in flight plans 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: used in flight plans | Statement: [SU95, aircraftIcaoCodeScope, used in flight plans]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: aircraftIcaoCodeScope
Context triple: [SU95, aircraftIcaoCodeScope, used in flight plans]
  • A. ICAOEngineCode
    Indicates that an engine is identified or classified by a specific ICAO (International Civil Aviation Organization) engine code.
  • B. associatedWithICAOcode
    Indicates a relationship where an entity is linked to, or identified by, a specific ICAO (International Civil Aviation Organization) code.
  • C. ICAOTypeDesignator chosen
    Indicates the standardized aircraft type code assigned by ICAO that specifies the model or family of an aircraft used in aviation operations and documentation.
  • D. airlineICAOcallsign
    Indicates the official ICAO radio callsign phrase used to identify a specific airline in air traffic communications.
  • E. isCivilAviationCode
    Indicates that a given code is designated as a civil aviation identifier for an airline, airport, or related aviation entity.
  • 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_69d8b9f79d14819095540856928f0e25 completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e4ad97611c8190a861467ae51f6c48 completed April 19, 2026, 10:25 a.m.
PD Predicate disambiguation batch_69e3f8f2bd088190b1e22ad4d9cc8b13 completed April 18, 2026, 9:34 p.m.
Created at: April 10, 2026, 10:21 a.m.