Triple

T4167551
Position Surface form Disambiguated ID Type / Status
Subject KADW E84479 entity
Predicate hasStandardTerminalArrivalRoutes P54459 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: [KADW, hasStandardTerminalArrivalRoutes, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasStandardTerminalArrivalRoutes
Context triple: [KADW, hasStandardTerminalArrivalRoutes, yes]
  • A. hasBoardingGatesFor
    Indicates that a location or facility provides designated boarding gates used for embarking passengers onto specific transportation services (such as flights or trains).
  • B. hasDomesticTerminal
    Indicates that a transportation facility, typically an airport, includes a terminal dedicated to domestic (within-country) travel operations.
  • C. hasInternationalTerminal
    Indicates that a transportation facility includes a terminal specifically designated for handling international arrivals and departures.
  • D. hasRunwayApproachType
    Indicates the specific type or category of approach procedure associated with a runway.
  • E. hasPassengerTerminalFunction
    Indicates that something serves the role or performs the function of a passenger terminal, supporting the handling and movement of passengers.
  • F. None of above. chosen

Provenance (4 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_69aed932cab48190b80ffe35f7029ae1 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69af02c43a7481909eed7cb8c14deb0c completed March 9, 2026, 5:26 p.m.
PD Predicate disambiguation batch_69af018fb0948190a9701b2e8e5d9bac completed March 9, 2026, 5:21 p.m.
PDg Predicate description generation batch_69af01ee94ec8190aa6dde54d4571c04 completed March 9, 2026, 5:22 p.m.
Created at: March 9, 2026, 3:44 p.m.