Triple

T10141219
Position Surface form Disambiguated ID Type / Status
Subject Salekhard Airport E231586 entity
Predicate servesCityPopulation P3936 FINISHED
Object residents of Salekhard 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: residents of Salekhard | Statement: [Salekhard Airport, servesCityPopulation, residents of Salekhard]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: servesCityPopulation
Context triple: [Salekhard Airport, servesCityPopulation, residents of Salekhard]
  • A. servedCity chosen
    Indicates that a service, route, or facility operates in, reaches, or is available to a particular city.
  • B. alternativeCityServed
    Indicates that one city functions as an alternative service location for another city, typically in contexts like transportation or logistics.
  • C. cityPopulationContext
    Indicates the contextual relationship between a city and information about its population, such as size, distribution, or demographic characteristics.
  • D. majorPopulationIn
    Indicates that a significant portion of a population is located in or primarily associated with a particular place or region.
  • E. cityServedType
    Indicates the type or category of city that is served by a given entity (such as a facility, service, or infrastructure).
  • 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_69ca848364f881908a24366a6feec1db completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cdeb2599e0819090184631e481310c completed April 2, 2026, 4:05 a.m.
PD Predicate disambiguation batch_69cd4ba4f5d88190ba68e63be10b08c7 completed April 1, 2026, 4:45 p.m.
Created at: March 30, 2026, 9:07 p.m.