Triple

T3146547
Position Surface form Disambiguated ID Type / Status
Subject TUI Group (historical) E65777 entity
Predicate hadSubsidiary P9212 FINISHED
Object TUIfly 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: TUIfly | Statement: [TUI Group (historical), hadSubsidiary, TUIfly]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: TUIfly
Context triple: [TUI Group (historical), hadSubsidiary, TUIfly]
  • A. 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.
  • B. Ryanair
    Ryanair is a major Irish low-cost airline known for its extensive network of short-haul flights across Europe.
  • C. Wizz Air
    Wizz Air is a Hungarian ultra-low-cost airline known for operating an extensive network of budget flights across Europe and surrounding regions.
  • D. Flynas
    Flynas is a Saudi low-cost airline based in Riyadh that operates domestic and regional flights across the Middle East and beyond.
  • E. Flybe
    Flybe was a British regional airline that operated short-haul flights across the UK and Europe before ceasing operations.
  • 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_69ad8582f564819088c27e1f96153938 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ada598ccf08190b8817c456f38f2d7 completed March 8, 2026, 4:36 p.m.
NED1 Entity disambiguation (via context triple) batch_69b276edde308190b26ac47ae1a79ce1 completed March 12, 2026, 8:18 a.m.
Created at: March 8, 2026, 3:05 p.m.