Triple

T32563142
Position Surface form Disambiguated ID Type / Status
Subject Frontier Miles E832280 entity
Predicate redemptionPricingModel P163428 FINISHED
Object dynamic pricing 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: dynamic pricing | Statement: [Frontier Miles, redemptionPricingModel, dynamic pricing]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: redemptionPricingModel
Context triple: [Frontier Miles, redemptionPricingModel, dynamic pricing]
  • A. redemptionModel chosen
    Indicates a relationship where one entity specifies or uses a particular model, method, or scheme for redeeming another entity (such as points, vouchers, or obligations).
  • B. redemptionType
    Indicates the manner or method by which something (such as a benefit, reward, or obligation) can be redeemed or fulfilled.
  • C. redemptionRate
    Indicates the proportion or frequency at which something (such as points, coupons, or investments) is redeemed relative to the total available or issued.
  • D. redemptionOptions
    Indicates the ways or methods by which something (such as points, credits, or vouchers) can be redeemed or exchanged for value.
  • E. redemptionFrequency
    Indicates how often a redemption action or event occurs within a given time period.
  • 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_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.
Created at: May 1, 2026, 1:03 a.m.