Triple

T10752891
Position Surface form Disambiguated ID Type / Status
Subject Scoot E253614 entity
Predicate offersAncillaryServices P9404 FINISHED
Object paid seat selection 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: paid seat selection | Statement: [Scoot, offersAncillaryServices, paid seat selection]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: offersAncillaryServices
Context triple: [Scoot, offersAncillaryServices, paid seat selection]
  • A. offersServiceIn
    Indicates that a provider makes a particular service available within a specified location or jurisdiction.
  • B. offersFeature chosen
    Indicates that one entity provides or makes available a particular feature or capability to another entity.
  • C. offeredService
    Indicates that one entity has provided or made available a service to another entity.
  • D. offersServiceType
    Indicates that one entity provides or makes available a specific type or category of service to another entity or the public.
  • E. hasPassengerServicesTo
    Indicates that a transportation provider operates passenger services connecting one location or entity to another.
  • 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_69d6aa5e51e8819095f06881cecf152e completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d71dc184d0819085f8bc4edb034377 completed April 9, 2026, 3:32 a.m.
PD Predicate disambiguation batch_69d6f30df9948190ab3cdc33977fac14 completed April 9, 2026, 12:30 a.m.
Created at: April 8, 2026, 9:15 p.m.