Triple

T20137841
Position Surface form Disambiguated ID Type / Status
Subject EETN E491070 entity
Predicate servesAsHubFor P423 FINISHED
Object airBaltic 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: airBaltic | Statement: [EETN, servesAsHubFor, airBaltic]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: airBaltic
Context triple: [EETN, servesAsHubFor, airBaltic]
  • A. airBaltic chosen
    airBaltic is the flag carrier airline of Latvia, operating a network of flights across Europe and beyond from its main hub in Riga.
  • B. Crossair
    Crossair was a former Swiss regional airline that served as the main predecessor to Swiss International Air Lines after the collapse of Swissair.
  • C. Atlantic Airways
    Atlantic Airways is the national airline of the Faroe Islands, operating domestic helicopter services and international flights primarily within Europe.
  • D. Lynx Air
    Lynx Air is a Canadian ultra-low-cost airline that operates domestic and select international flights, primarily serving major hubs such as Toronto Pearson International Airport.
  • E. Hunnu Air
    Hunnu Air is a Mongolian airline that operates domestic and regional international flights, primarily serving as a key carrier based in Ulaanbaatar.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69da62651a0c8190a3e05e95e056a66b completed April 11, 2026, 3:01 p.m.
NER Named-entity recognition batch_69e6676879f48190a59da04393d2a8cc completed April 20, 2026, 5:50 p.m.
Created at: April 11, 2026, 11:32 p.m.