Triple

T327927
Position Surface form Disambiguated ID Type / Status
Subject Geneva Airport E6559 entity
Predicate supportsDomesticFlights P1658 FINISHED
Object yes 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: yes | Statement: [Geneva Airport, supportsDomesticFlights, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsDomesticFlights
Context triple: [Geneva Airport, supportsDomesticFlights, yes]
  • A. hasDomesticFlights chosen
    Indicates that an airline or airport operates flights within the same country, connecting domestic destinations.
  • B. hasInternationalFlights
    Indicates that an airport or airline operates flights connecting to destinations in other countries.
  • C. hasLongHaulFlights
    Indicates that an entity (such as an airline, route, or airport) operates or is associated with long-distance flights typically covering intercontinental or extended-duration journeys.
  • D. servesAirlineType
    Indicates that a service provider (such as an airport, terminal, or facility) accommodates or operates flights for a specified type or category of airline.
  • E. airSupport
    Indicates that one entity provides aerial assistance or backing to another, typically through aircraft-based protection, transport, or attack.
  • 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_69a2e7933d6c8190bb2592ad13286ef2 completed Feb. 28, 2026, 1:03 p.m.
NER Named-entity recognition batch_69a2ea98fa2c8190a5b44f4a26543a17 completed Feb. 28, 2026, 1:16 p.m.
PD Predicate disambiguation batch_69a2e94aab1c8190b8654708c87eeb91 completed Feb. 28, 2026, 1:10 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.