Triple

T782254
Position Surface form Disambiguated ID Type / Status
Subject TUI Airways E16522 entity
Predicate formerName P65 FINISHED
Object Thomson Airways E16522 NE 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: Thomson Airways | Statement: [TUI Airways, formerName, Thomson Airways]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Thomson Airways
Context triple: [TUI Airways, formerName, Thomson Airways]
  • A. Loganair
    Loganair is a Scottish regional airline that operates domestic and short-haul international flights across the United Kingdom and nearby destinations.
  • B. Sky Airline
    Sky Airline is a Chilean low-cost carrier that operates domestic and regional flights across South America.
  • C. Ibex Airlines
    Ibex Airlines is a Japanese regional airline that operates domestic routes, often connecting smaller cities and regional airports within Japan.
  • D. TUI Airways chosen
    TUI Airways is a British charter and scheduled airline that primarily serves leisure destinations across Europe and worldwide as part of the TUI Group.
  • E. Flair Airlines
    Flair Airlines is a Canadian ultra-low-cost carrier that operates domestic and select international flights, emphasizing budget-friendly travel options.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69a4936ad1fc81908f190208059ccf78 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a765ba688190ab328bb159583077 completed March 1, 2026, 8:53 p.m.
NED1 Entity disambiguation (via context triple) batch_69a79286e8b88190887def813bc65d95 completed March 4, 2026, 2:01 a.m.
Created at: March 1, 2026, 7:37 p.m.