Triple

T34506293
Position Surface form Disambiguated ID Type / Status
Subject Livingstone Airport E885895 entity
Predicate servesFlightsType P18239 FINISHED
Object scheduled passenger flights 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: scheduled passenger flights | Statement: [Livingstone Airport, servesFlightsType, scheduled passenger flights]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: servesFlightsType
Context triple: [Livingstone Airport, servesFlightsType, scheduled passenger flights]
  • A. 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.
  • B. servesFlightsTo
    Indicates that one transportation provider regularly operates flights to a specified destination location.
  • C. hasTypeOfFlights chosen
    Indicates that an entity offers, includes, or is associated with specific categories or kinds of flights.
  • D. servesAviationType
    Indicates that one entity provides services or functions specifically for a particular type or category of aviation.
  • E. servesAirportType
    Indicates that a transportation service or facility provides service to, or is designated for, a specific type or category of airport.
  • 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_69f349cc0220819081f154c6964f4dc2 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69ffb69812808190a751853b30183e65 completed May 9, 2026, 10:35 p.m.
PD Predicate disambiguation batch_69ffb63bdda88190a9dd8426dc0bad43 completed May 9, 2026, 10:33 p.m.
Created at: May 1, 2026, 2:01 a.m.