Triple

T4742311
Position Surface form Disambiguated ID Type / Status
Subject Leslie E105272 entity
Predicate hasPassengerWifi P8861 FINISHED
Object yes 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: yes | Statement: [Leslie, hasPassengerWifi, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPassengerWifi
Context triple: [Leslie, hasPassengerWifi, yes]
  • A. offersInFlightWiFi chosen
    Indicates that an entity provides wireless internet access to passengers during a flight.
  • B. hasPassengerServicesTo
    Indicates that a transportation provider operates passenger services connecting one location or entity to another.
  • C. hasPassengerInformationSystem
    Indicates that an entity is equipped with a system that provides information to passengers, such as schedules, announcements, or travel updates.
  • D. hasPassengerArea
    Indicates that an object or vehicle includes a designated area intended for carrying passengers.
  • E. hasPassengerOnlyService
    Indicates that the service provided involves only the transportation of passengers, with no freight or cargo component.
  • 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_69bd43ef87a48190a5bc3600711aa032 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd64a7153881909eac451fc7566d25 completed March 20, 2026, 3:15 p.m.
PD Predicate disambiguation batch_69bd6221c3b881908604f35f8de6f16b completed March 20, 2026, 3:05 p.m.
Created at: March 20, 2026, 1:19 p.m.