Triple

T5644692
Position Surface form Disambiguated ID Type / Status
Subject Tacoma Narrows Airport E124355 entity
Predicate hasCommercialAirlineService P49167 FINISHED
Object no 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: no | Statement: [Tacoma Narrows Airport, hasCommercialAirlineService, no]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCommercialAirlineService
Context triple: [Tacoma Narrows Airport, hasCommercialAirlineService, no]
  • A. hasAirlines
    Indicates that one entity (such as an airport, city, or country) is served by or associated with one or more airline operators.
  • B. 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.
  • C. servesAirline
    Indicates that a transportation facility or location provides service for, or is regularly used by, a specified airline.
  • D. hasPassengerServicesTo
    Indicates that a transportation provider operates passenger services connecting one location or entity to another.
  • E. isCommercialServiceAirport chosen
    Indicates that an airport is designated and operated as a commercial service facility offering scheduled passenger or cargo air transport 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_69c00824643c81909ffdb888a2d35189 completed March 22, 2026, 3:17 p.m.
NER Named-entity recognition batch_69c022a8eccc8190837d4705670dc25e completed March 22, 2026, 5:11 p.m.
PD Predicate disambiguation batch_69c01b2168508190b64b355cf50034ad completed March 22, 2026, 4:38 p.m.
Created at: March 22, 2026, 3:41 p.m.