Triple

T1458500
Position Surface form Disambiguated ID Type / Status
Subject SkyTeam Elite Plus E31452 entity
Predicate loungeAccessCondition P13902 FINISHED
Object same-day departure on a SkyTeam-operated flight 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: same-day departure on a SkyTeam-operated flight | Statement: [SkyTeam Elite Plus, loungeAccessCondition, same-day departure on a SkyTeam-operated flight]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: loungeAccessCondition
Context triple: [SkyTeam Elite Plus, loungeAccessCondition, same-day departure on a SkyTeam-operated flight]
  • A. hasCustomerLounge
    Indicates that an entity provides or includes a designated lounge area for customers to use.
  • B. hasLoungeBrand
    Indicates that an entity is associated with, or operates under, a particular lounge brand.
  • C. authorizationCondition chosen
    Indicates the specific rules or requirements that must be satisfied for an action or access to be legally or formally authorized.
  • D. accessibleFrom
    Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
  • E. areAccessibleAt
    Indicates that certain entities can be reached, used, or entered at a specified location, time, or context.
  • 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_69a49917dfc081909acdbdf5d684f1ef completed March 1, 2026, 7:52 p.m.
NER Named-entity recognition batch_69a4c59a462881908e84b27846a6bc04 completed March 1, 2026, 11:02 p.m.
PD Predicate disambiguation batch_69a4c47ec5108190b1772237f2e5d90b completed March 1, 2026, 10:58 p.m.
Created at: March 1, 2026, 8 p.m.