Triple

T26115743
Position Surface form Disambiguated ID Type / Status
Subject EGCN E658819 entity
Predicate associatedAirportStatus P48854 FINISHED
Object closed to commercial passenger traffic 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: closed to commercial passenger traffic | Statement: [EGCN, associatedAirportStatus, closed to commercial passenger traffic]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: associatedAirportStatus
Context triple: [EGCN, associatedAirportStatus, closed to commercial passenger traffic]
  • A. airportStatus chosen
    Indicates the current operational condition or state of an airport (e.g., open, closed, delayed, restricted).
  • B. associatedAirportStateOrUT
    Indicates that an airport is located within or linked to a specific state or union territory.
  • C. airlineStatus
    Indicates the current operational or membership state of an airline, such as its activity, certification, or alliance standing.
  • D. formerAirportStatus
    Indicates that an entity previously held the status of an airport but no longer functions as one.
  • E. cityTerminalStatus
    Indicates the operational or functional status of a city’s terminal (such as an airport, bus, or train terminal) within a given context or system.
  • 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_69ee5bc20298819099a42be042eb2349 completed April 26, 2026, 6:38 p.m.
NER Named-entity recognition batch_69feb342994081909481ec8ec5d44928 completed May 9, 2026, 4:08 a.m.
PD Predicate disambiguation batch_69feb046e4e48190b96649aa28529cc9 completed May 9, 2026, 3:55 a.m.
Created at: April 26, 2026, 8:05 p.m.