Triple

T10873318
Position Surface form Disambiguated ID Type / Status
Subject Hosea Kutako International Airport E256710 entity
Predicate hasAirportLounge P13530 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: [Hosea Kutako International Airport, hasAirportLounge, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAirportLounge
Context triple: [Hosea Kutako International Airport, hasAirportLounge, yes]
  • A. hasCustomerLounge chosen
    Indicates that an entity provides or includes a designated lounge area for customers to use.
  • B. hasLoungeType
    Indicates that an entity is associated with, or classified by, a particular type or category of lounge.
  • C. hasLoungeBrand
    Indicates that an entity is associated with, or operates under, a particular lounge brand.
  • D. isLocatedAtAirportType
    Indicates that one entity is situated at, or associated with, an airport of a specified type (e.g., international, regional, military).
  • E. hasDomesticConcourse
    Indicates that a transportation facility includes a concourse area designated for domestic (within-country) passengers or services.
  • 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_69d6aa848804819081b2713ca0bedf06 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d751891b508190959784f212e06acb completed April 9, 2026, 7:13 a.m.
PD Predicate disambiguation batch_69d70d360c388190a3d829fe8862434f completed April 9, 2026, 2:21 a.m.
Created at: April 8, 2026, 9:21 p.m.