Triple

T28018024
Position Surface form Disambiguated ID Type / Status
Subject Laishevo District E707602 entity
Predicate hasAirportServingArea P17216 FINISHED
Object Kazan International Airport NE NERFINISHED

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: Kazan International Airport | Statement: [Laishevo District, hasAirportServingArea, Kazan International Airport]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAirportServingArea
Context triple: [Laishevo District, hasAirportServingArea, Kazan International Airport]
  • A. airportServed
    Indicates that a particular airport provides service to, or is used for air travel to and from, a given location or area.
  • B. associatedAirportServes
    Indicates that a given airport provides service to, or is used by, the associated entity (such as a city, region, or facility).
  • C. airportServesAs
    Indicates that an airport functions in a particular role or capacity (such as primary, secondary, or hub) for a specified area, organization, or service.
  • D. hasRegionalAirport chosen
    Indicates that a place or region possesses or is served by a regional airport.
  • E. hasAirportWithinJurisdiction
    Indicates that a governing authority or administrative region has legal or administrative control over an airport located within its boundaries.
  • 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_69ef96baf3a881909a2b63844185dddd completed April 27, 2026, 5:02 p.m.
NER Named-entity recognition batch_69f65876c52c8190bc889c7a67bd07f3 completed May 2, 2026, 8:03 p.m.
PD Predicate disambiguation batch_69f6575d89788190aca478e4aea05a65 completed May 2, 2026, 7:58 p.m.
Created at: April 27, 2026, 8:08 p.m.