Triple

T19402349
Position Surface form Disambiguated ID Type / Status
Subject NGTE E485358 entity
Predicate hasRunwayUseAtAssociatedAirport P19339 FINISHED
Object domestic flights 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: domestic flights | Statement: [NGTE, hasRunwayUseAtAssociatedAirport, domestic flights]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRunwayUseAtAssociatedAirport
Context triple: [NGTE, hasRunwayUseAtAssociatedAirport, domestic flights]
  • A. hasRunwayUse chosen
    Indicates that a particular runway is authorized or designated for use by a specific aircraft, operation, or purpose.
  • B. hasRunwayAccessTo
    Indicates that one location or facility is directly connected to another via a usable runway, allowing aircraft to move between them without leaving runway infrastructure.
  • C. hasRunwayAccessVia
    Indicates that an entity has access to a runway by means of a specified connecting route, facility, or intermediary.
  • D. hasRunwayOperations
    Indicates that an entity conducts or is involved in operational activities on an airport runway, such as takeoffs, landings, or related ground movements.
  • E. hasRunwayPresence
    Indicates that an entity maintains a physical runway or landing strip suitable for aircraft operations.
  • 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_69d8e8d5162481909db12435d9535c1a completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e62577f808819099e74feab82b34a4 completed April 20, 2026, 1:09 p.m.
PD Predicate disambiguation batch_69e4fd68b1f881908d273de1fee81a75 completed April 19, 2026, 4:06 p.m.
Created at: April 10, 2026, 1:36 p.m.