Triple

T32563134
Position Surface form Disambiguated ID Type / Status
Subject Frontier Miles E832280 entity
Predicate eliteStatusBenefitsInclude P174599 FINISHED
Object priority boarding 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: priority boarding | Statement: [Frontier Miles, eliteStatusBenefitsInclude, priority boarding]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: eliteStatusBenefitsInclude
Context triple: [Frontier Miles, eliteStatusBenefitsInclude, priority boarding]
  • A. eliteStatusProgram
    Indicates a relationship where an entity is enrolled in or associated with a special high-tier or privileged status program.
  • B. exclusiveBenefit
    Indicates that a benefit is provided to one party or group in a way that excludes others from receiving the same advantage.
  • C. isTopTierBenefit
    Indicates that a benefit belongs to the highest or most premium level within a defined benefit hierarchy or structure.
  • D. benefitsLevel
    Indicates the degree or extent to which one entity gains advantages, support, or positive outcomes from another entity or action.
  • E. VIPStatus
    Indicates that an entity holds a special or privileged status compared to others, often granting enhanced access, benefits, or priority treatment.
  • F. None of above. chosen

Provenance (4 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_69f34926b9848190ace47d2dd0a0de7c completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6c609f1c08190830b42dc4df5ab8d completed May 3, 2026, 3:50 a.m.
PD Predicate disambiguation batch_69f6bd2a14b081908162923dfbf0a6f4 completed May 3, 2026, 3:12 a.m.
PDg Predicate description generation batch_69f6c1b666188190ac43c3011a7df048 completed May 3, 2026, 3:32 a.m.
Created at: May 1, 2026, 1:03 a.m.