Triple

T10155381
Position Surface form Disambiguated ID Type / Status
Subject Flynas E232761 entity
Predicate offersBookingChannel P30179 FINISHED
Object online booking via website 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: online booking via website | Statement: [Flynas, offersBookingChannel, online booking via website]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: offersBookingChannel
Context triple: [Flynas, offersBookingChannel, online booking via website]
  • A. hasBookingChannel
    Indicates that an entity is associated with or obtained through a particular method or platform used to make a booking.
  • B. offersDestination
    Indicates that one entity provides or makes available another entity as a possible destination.
  • C. airlineBookingChannel chosen
    Indicates the method or platform through which an airline reservation is made or managed between a customer and the airline.
  • D. alsoBookableAs
    Indicates that one entity can be reserved or booked in an alternative way or under an alternative option represented by another entity.
  • E. bookingOption
    Indicates a selectable arrangement or choice available for making a booking, such as a specific time, package, or set of conditions under which a reservation can be made.
  • 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_69ca84885e48819088a31b127cf44904 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cdec3a5e7c819098b2f9ccbde7cf94 completed April 2, 2026, 4:10 a.m.
PD Predicate disambiguation batch_69cd4ba795808190acc9124c98c6e40f completed April 1, 2026, 4:45 p.m.
Created at: March 30, 2026, 9:09 p.m.