Triple

T4529033
Position Surface form Disambiguated ID Type / Status
Subject Flybe E106248 entity
Predicate renamedAs P65 FINISHED
Object Flybe E106248 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: Flybe | Statement: [Flybe, renamedAs, Flybe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Flybe
Context triple: [Flybe, renamedAs, Flybe]
  • A. Flybe chosen
    Flybe was a British regional airline that operated short-haul flights across the UK and Europe before ceasing operations.
  • B. Flynas
    Flynas is a Saudi low-cost airline based in Riyadh that operates domestic and regional flights across the Middle East and beyond.
  • C. Ryanair
    Ryanair is a major Irish low-cost airline known for its extensive network of short-haul flights across Europe.
  • D. TUI Airways
    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. Loganair
    Loganair is a Scottish regional airline that operates domestic and short-haul international flights across the United Kingdom and nearby destinations.
  • 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_69bd43f3d6e08190a91824f833d51bbe completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd5779593081908593537b9239e01b completed March 20, 2026, 2:19 p.m.
NED1 Entity disambiguation (via context triple) batch_69bdc55254848190940c506e75d79933 completed March 20, 2026, 10:08 p.m.
Created at: March 20, 2026, 1:03 p.m.